RE: [FAQ] Linking to separate libraries per-architecture [was: Problem Building x86 Project on PowerPC]
RE: [FAQ] Linking to separate libraries per-architecture [was: Problem Building x86 Project on PowerPC]
- Subject: RE: [FAQ] Linking to separate libraries per-architecture [was: Problem Building x86 Project on PowerPC]
- From: "Matthew Douglass" <email@hidden>
- Date: Wed, 9 May 2007 10:07:06 -0700
> 3) If you must do it this way, set these two Custom
> Build Settings in your target (for all configurations):
>
> OTHER_LINKER_FLAGS_ppc = -l<path-to-ppc-dylib>
> OTHER_LINKER_FLAGS_i386 = -l<path-to-intel-dylib>
>
> (That's dash, ell, followed by the path)
>
> Then set the Other Linker Flags build setting for all
> configurations to
>
> $(OTHER_LINKER_FLAGS_$(CURRENT_ARCH))
>
> That instructs the linker to link your binary with
> different libraries for each of the ppc and i386 architectures.
Hey Chris (et al),
Just a follow-up question for my own education. When I setup my projects
for Universal I followed Apple's instructions in the Xcode guidelines.
Those instructions had me make similar settings using things like
GCC_VERSION_x86 and GCC_VERSION_ppc (GCC_VERSION just picked for example out
of the settings the docs suggest). However, those instructions did not have
the final step you just showed (and I've seen a couple times lately) of
setting GCC_VERSION to $(GCC_VERSION_$(CURRENT_ARCH)). Yet, everything
seemed to work correctly. Does Xcode do this automatically for some
settings and not for others? Or should I be adding the CURRENT_ARCH magic
for everything?
Thanks,
Matthew
_______________________________________________
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