• 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: linking to a styled private framework
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: linking to a styled private framework


  • Subject: Re: linking to a styled private framework
  • From: Fritz Anderson <email@hidden>
  • Date: Thu, 2 Jun 2005 22:35:44 -0500


On 2 Jun 2005, at 3:57 PM, Eric Slosser wrote:

With XCode 2.0, I'm building a plugin that uses a framework that is built by another XCode project on the same disk.

The plugin and framework both have the standard two build styles, development and deployment. Both projects have their build styles configured to build into different directories.
...
How can I get the plugin's XCode project configured so that the plugin gets the right flavor of the framework? No matter how I configure the plugin's project, build style, target, or how I add the framework to the project and set its path (relative to foo, etc), I can't get the linker to link to the framwork at $BUILD_PRODUCTS_DIR. It insists on doing something like ../../ Output/Release/, where 'Release' (vs. Debug) is determined by which style of the framework I picked when I added it to the project.

That the frameworks in the Release and Debug subdirectories of your shared build directory are related to each other is information in your head. That information is not anywhere in Xcode. When you tell Xcode that the framework at Output/Release is the framework you want, it assumes you don't want similarly named frameworks anywhere else. When you shift from Release to Debug, the location you originally specified is the location it uses, because it can't read your mind that you don't really mean that any more.


If you want to link against different frameworks (and two frameworks, with different configurations, in two different directories, _are_ different frameworks), then include both in the project, and specify one for the Release target and the other for the Debug target. You (basically) can't change the file set of a product by switching build styles; if the file set is different, you have to use different targets.

    -- F

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re:linking to a styled private framework
      • From: Eric Slosser <email@hidden>
References: 
 >linking to a styled private framework (From: Eric Slosser <email@hidden>)

  • Prev by Date: Re: Manual KVO and will/didChangeValueForKey
  • Next by Date: NSServices with files
  • Previous by thread: linking to a styled private framework
  • Next by thread: Re:linking to a styled private framework
  • Index(es):
    • Date
    • Thread