Re: Linker woes
Re: Linker woes
- Subject: Re: Linker woes
- From: Tim Murison <email@hidden>
- Date: Wed, 13 May 2009 10:09:01 -0400
- Thread-topic: Linker woes
> 1. Make sure you are using a shared build directory when you have
> multiple project files. It sounds like you might be, but make sure
> that that the build products from both projects are sitting in the
> same directory.
This is what I was doing before, but it is a mess. I want my build products
folder to be organized, something like:
Build/Debug/Tests
Build/Debug/Apps
Build/Debug/Frameworks
Build/Debug/Libraries
Etc...
> 2. Make sure that the configuration names are the same in both
> projects. If you are building the Debug configuration in "main" Xcode
> will build the Debug configuration in "common"
They are.
> 3. Do not use the "Add Existing Frameworks..." to add any of the
> libraries you create to your project. That command is for third party
> (i.e. don't change often) libraries, exclusively. Use the references
> in the "Products" group to drag to your "Link Binary with Libraries"
> build phase. If you are including libraries from the "common" project
> use the libraries that are revealed under the "common" xcode project.
> If you use these two locations, Xcode will link against the
> appropriate configuration for you. If you use the "Add Existing
> Frameworks..." it will use the absolute path you browsed to when
> completing that command.
I'm clean here too.
> 4. I wouldn't mess around with the CONFIGURATION_BUILD_DIR.
I needed to change this variable in order to produce the build artifacts in
the folders I want.
_______________________________________________
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