• 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
Aggregate Project and how to force targets to use a particular configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Aggregate Project and how to force targets to use a particular configuration


  • Subject: Aggregate Project and how to force targets to use a particular configuration
  • From: Alfred Van Hoek <email@hidden>
  • Date: Sun, 3 Sep 2006 10:28:25 -0400

Perhaps documented. But I have a pure aggregate project to which four xcode projects were added, 3 projects define static libs, and the other defines the final product as a dylib. Working from the aggregate works splendid, but how can I manage to change the configuration of the targets in the sub projects (targets are ppc and i386, currently set for deployment/release) to debug? The aggregate does not have a configuration to begin with...

Alfred
_______________________________________________
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: Aggregate Project and how to force targets to use a particular configuration
      • From: Scott Tooker <email@hidden>
  • Prev by Date: Re: Dumb code navigation question
  • Next by Date: Remote Debugging/exec paths
  • Previous by thread: Re: Dumb code navigation question
  • Next by thread: Re: Aggregate Project and how to force targets to use a particular configuration
  • Index(es):
    • Date
    • Thread