Re: Can you use Build Configurations to link with different libraries?
Re: Can you use Build Configurations to link with different libraries?
- Subject: Re: Can you use Build Configurations to link with different libraries?
- From: Dave Thorup <email@hidden>
- Date: Tue, 19 Jul 2005 17:36:39 -0400
On Jul 19, 2005, at 4:41 PM, Mark Bessey wrote: First, make a reference to your library project from the application project - Open the application project, and use the Project->Add to Project... menu item to add a reference to the library's xcode project file. You should be able to accept the default settings for adding a file, but make sure that "Copy items into destinations group's folder" is NOT checked.
Now that you have a reference from one project to the other, you should set up a dependency on the library target from the application target. Double-click the application target in the Groups & Files view, and use the "+" button on the "General" pane to set the application as being dependent on the library. (This isn't strictly necessary, but you'd normally want to have a dependency on the library, so if you change it, the application gets rebuilt, too.)
But what if you don't have access to the library's project? Only a few people actually have access to the library's project file, plus once the libraries are built, they are deployed to a different location that has less strict access privileges. The libraries are built to be used by a large amount of people, but only a select few actually have access to the source code and the project files.
Do you see any way for this to work in this type of scenario?
Thanks! _____________________________
Dave Thorup Software Engineer email@hidden
http://www.kuwan.net Defaults Manager - The premier editor for Mac OS X's User Defaults / Preferences database.
|
_______________________________________________
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