koobas.hobune.stream
IPad Simulator compile error, it can't seem to find my directories.
In unity Phone 1.7 I am getting hundrads of warnings and 28 errors. they all seem to stem from these two warnings about not finding directories.
ld: warning: directory '"/Users/grantmorgan/Documents/unity/AmirGame/ipadBlocksSim"' following -L not found
ld: warning: directory '"/Users/grantmorgan/Documents/unity/AmirGame/ipadBlocksSim/Libraries"' following -L not found
The directories are there. I've rebooted a couple of times. I have SDK 4.0 with 3.2 installed. Any suggestions of what else to try.
Cheers, Grant
Did you find a solution for this? I get the same 200+ warnings and 28 errors...
It's a long shot but try to Clean All Targets and build with 3.2.
Is this after installing on the device or in the simulator, you will eventually haveto change these directories to ones in your "sandbox" for your application bundel.
- This may also be a permission error try chmod -R 777 /*/yourproject
- Then if it isn't fixed try reimporting you entire project folder be selecting everything in the project view and using the "Assets->Reimport" menu
- If all else fails simply restore from you last working backup, which hopefully isn't to out of date( if it is lesson learned, back up more frequently).
Thanks but none of these suggestions work for me. This happens when trying to build for the simulator (haven't tried device yet). It should find the directories because the next warning in the list is
ld: warning: Nx$$anonymous$$at33::fromQuat(NxQuat const&)has different visibility (default) in //myproject/Libraries/libiPhone-lib.a(ContactCapsuleHeightField.o) and (hidden) in //myproject/Libraries/libiPhone-lib.a(Collider.o)
So if I am to understand it is not in fact unity that returns these errors, but rather xcode then the solution is different. Building for the simulator is generally a problem, building for the device usually simplifies things. The first step is to try the different active configurations(debug,release), release usually makes it run. Also try disabling code stripping, it removes debug symbols used by the simulator. You may also try tweaking your simulator target configuration. Using the device is necessary before final release, is easier to test on, and does not usually cause such errors.
