Re: Why does Xcode create nonsensical destinations in every scheme?
Re: Why does Xcode create nonsensical destinations in every scheme?
- Subject: Re: Why does Xcode create nonsensical destinations in every scheme?
- From: G S <email@hidden>
- Date: Tue, 24 May 2011 21:29:23 -0700
>If you end up needing to do this again in the future, you should be able to do conditional target linker flags. Thus you can create a rule that conditionally links Debug/Simulator, Debug/Device, Release/Simulator, Release/Device without needing a second target.
Looks like I do need this. I'm using a pre-built OpenSSL lib, and after I deleted one of the targets and schemes, I'm getting "missing architecture" complaints:
ld: warning: ignoring file /Volumes/software & work/projects/Stashpix/app/Stashpix/lib/libcrypto-device.a, missing required architecture i386 in file
Undefined symbols for architecture i386:
"_BIO_f_base64", referenced from:
But that architecture and those symbols are defined in the simulator version of the lib, which is also included in the project (which wasn't ignored). So I don't know
A. Why it's not finding the symbols in the included i386 lib.
B. Why it worked before with two targets. I don't see any specific references to libs in the build settings.
Given that libs with inappropriate architectures are automatically ignored, I shouldn't even need any architecture-specific linker flags.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden