Re: adding a static library in another project relative to my build product
Re: adding a static library in another project relative to my build product
- Subject: Re: adding a static library in another project relative to my build product
- From: Roland King <email@hidden>
- Date: Fri, 2 Oct 2009 00:02:41 +0800
Thanks Jens, let me go mess with that, I didn't think of drag-dropping
the project.
On 01-Oct-2009, at 11:35 PM, Jens Alfke wrote:
On Oct 1, 2009, at 7:15 AM, Roland King wrote:
I have a library which is built in \Users\me\Code\MyLib\build
\<product type>\libMyLib.ar
Now I have a project which uses it, \Users\my\Code\MyApp\
and try as I might I can't find a way to include it so that
whatever product type I'm building, I pick up the correct version
of the library for that build product. The 'relative to' bit is
always on the start of the path, I need it in the middle of the path.
Add the project that builds the library to the project that uses it
(just drag the project file into the other project's source list.)
Then you can edit the settings of the target that uses the library,
and (a) add the library to the set of libraries it imports, and (b)
specify a dependency on the target that builds the library.
This will automatically take care of getting the library out of the
appropriate Debug/Release build folder, and it will even make sure
to build the library first if any of its source files have changed.
—Jens
_______________________________________________
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