• 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
per-project dependent project build settings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

per-project dependent project build settings


  • Subject: per-project dependent project build settings
  • From: Roland King <email@hidden>
  • Date: Sun, 13 Apr 2014 19:39:44 +0800

I have a huge library I've built up over time containing all my fun bits of code. That's in its own project. When I want to use the library I add the xcodeproj file into the project I want to use it in, set up a few build variables and make it a dependency and everything is fine. This is a static library, I started using it for iOS originally so static it has stayed. The final binary just links in whatever bits it needed.

The library project is set to build to 'latest OSX', so currently 10.9, with a Deployment Target default, so again 10.9.

I have a project I want to use the library for which needs to build with a Deployment Target of 10.7. I've imported the library project in the usual way and set all the target deployment stuff to 10.7 however the library dependency is still building with its own settings, of 10.9, which means it uses _objc_setProperty_atomic which then fails deployed on 10.7.

Is there a way I can get the library project to build with a different Deployment Target in this one overall project? It's building its own copy of the library in the project build directory, not like it needs to share it with any other piece of code. I obviously don't want to change the deployment target of the library in the library project as that changes it for everyone, nor do I want to keep toggling it up and down when I build different projects.

I could add a separate target, library_10_7 but that seems really hokey and unscalable. I poked around with Workspaces a bit but that didn't seem to offer more options and indeed projects there sit side-by-side with each other as top-level objects, at least in the current case the library project is 'inside' the outer one which gave me so home the 'outer' project settings could be forced into the dependencies.

Any way I can do this?

 _______________________________________________
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


  • Follow-Ups:
    • Re: per-project dependent project build settings
      • From: Damian Carrillo <email@hidden>
  • Prev by Date: Re: How big is the Xcode 5.1.1 download?
  • Next by Date: Re: per-project dependent project build settings
  • Previous by thread: Re: How big is the Xcode 5.1.1 download?
  • Next by thread: Re: per-project dependent project build settings
  • Index(es):
    • Date
    • Thread