On Apr 21, 2005, at 10:26 AM, Andrew Kimpton wrote:
I have a project which builds a bundle, it in turn includes two 'sub
projects' as dependant targets - each a static library of common code.
It seems like the build style I pick for the 'top level' project
propogates to the sub projects not merely as a 'label' (ie use the
Deployment style from the libblah.xcode project) but as a concrete
set of build options.
This means that a -lxtra_lib flag I specify only in the deployment
build style (using Other Linker Flags) for the top level target is
being passed to the libtool command line of the two subprojects. I
don't want that extra library linked when I build the two
subprojects (aside from the library paths not being set correctly to
find it I don't think libtool allows for a string of .o files to be
combined with another .a archive to create a new .a archive ?)
Is this a known bug with a workaround ?
Andrew 8-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
