Weak Linking vs. Distributed Builds (was Re: __builtin___CFStringMakeConstantString vs. Mac OS X Deployment Target)
Weak Linking vs. Distributed Builds (was Re: __builtin___CFStringMakeConstantString vs. Mac OS X Deployment Target)
- Subject: Weak Linking vs. Distributed Builds (was Re: __builtin___CFStringMakeConstantString vs. Mac OS X Deployment Target)
- From: Jim Correia <email@hidden>
- Date: Wed, 17 Mar 2004 11:49:18 -0500
On Mar 15, 2004, at 2:08 PM, Jim Correia wrote:
I want to set the Deployment Target to 10.2 so that 10.3 only symbols
will be weak linked. But when I do this I get a compiler error of the
form:
error: built-in function `__builtin___CFStringMakeConstantString'
requires `-fconstant-cfstrings' flag
(I'm working with the Carbon project template as is for purposes of
testing this.)
Am I missing something else? Should the value of
__CONSTANT_CFSTRINGS__ used in CFString.h be updated accordingly when
using an older deployment target? (I cannot use the 10.2.7 SDK because
I need 10.3 APIs.)
Turns out this is related to using distributed builds. If I turn off
distributed builds everything works correctly. If I turn distributed
builds back on I get the error (and presumably functions not compiled
with the weak attribute, etc.)
Is the env var (MACOSX_DEPLOYMENT_TARGET ) not packaged up and sent to
the remote machine?
Known bug? (I filed it as rdar://3590291 )
Workaround?
Thanks,
Jim
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.