• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Attach library (.a) in Xcode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Attach library (.a) in Xcode


  • Subject: Re: Attach library (.a) in Xcode
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Thu, 26 Jun 2008 19:27:43 +0200


Le 26 juin 08 à 19:11, Sebastian Nowicki a écrit :


On 26/06/2008, at 11:58 PM, Jean-Daniel Dupas wrote:

An new usefull feature of Xcode 3.0 is "Composite SDKs":

“You can now specify multiple SDKs; for example, a system SDK, a QuickTime SDK, and the SDK for a third-party library or framework. To do this, set the Base SDK Path build setting to a system SDK and set the Additional SDKs build setting to the list of additional SDKs to composite. At build time Xcode will create a composite SDK and cache it in a common location; all projects that use that combination will share the one composite SDKs. This allows you, for example, to use libraries provided by third parties when building against a system SDK.”

I did a folder like this: MySDK.sdk/usr/include and MySDK.sdk/usr/ lib wich contains custom static libraries and headers I do not want to install on the OS. Then I add the MySDK folder to the list of additional SDK, and I can use my custom libraries without having to adjust header search path and library search path for each target.

That sounds pretty good. I think I'll try that out when I get time. There's still one question to be answered though; would the SDK be tracked under an SCM? It seems logical to checkout the full tree without having to build the SDK (or whatever) yourself, and have a consistent version, but it doesn't make much sense to track a 3rd party library, especially if the about of changes is large (which would bloat the size of the repository). I'm divided by the two. Currently I just put the headers and static libraries under a Libraries/ directory and add this directory to the header/library search paths for the target. The directory is tracked under the SCM, but doesn't get updated often.

I don't think there is general rule about it. Some will put the SDK into an SCM, other will just share the SDK using an AFP server.
The last time I had to configure such system, I did a separate SCM repository for shared resources, so the main repository was not bloated, and everybody was able to sync the SDK on each machine.



Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

References: 
 >Attach library (.a) in Xcode (From: "dexter morgan" <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: Jens Alfke <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: "Sherm Pendley" <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: Sebastian Nowicki <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: Rush Manbert <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Attach library (.a) in Xcode (From: Sebastian Nowicki <email@hidden>)

  • Prev by Date: Re: Interface Builder - Large Fonts
  • Next by Date: Re: Build & Go starts IB
  • Previous by thread: Re: Attach library (.a) in Xcode
  • Next by thread: multiple definitions errors
  • Index(es):
    • Date
    • Thread