• 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
Indirect framework reference problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Indirect framework reference problems


  • Subject: Indirect framework reference problems
  • From: Mike Laster <email@hidden>
  • Date: Sun, 1 Feb 2004 19:08:48 -0500

In our current build environment (about 100 projects), we do a "build and install" process to build up our system. While this works, I'm trying to migrate to a style where things are run out of the development directories and nothing has to be installed in it's final location. I've been told often that Project Builder (and now Xcode) support this.

However, I'm running into a problem with indirect framework dependencies. For instance, if I have 2 projects:

'FrameworksA' and  'CommandLineTool'

and I have my build products location set to "$(HOME)/Library/Caches/Xcode"

FrameworkA only depends on standard Apple frameworks, and CommandLineTool depends on FrameworkA (and Apple stuff).
I list '/Marketocracy/Frameworks/FrameworkA.framework' as a framework reference in the CommandLineTool project to make it
link against it. This works, even if I don't actually install FrameworkA, since Xcode does the magic behind the scenes to actually
look in the build products directory to find the framework.


Now imagine at some later point FrameworkA gets some new functionality, and in the process, it gains a dependency on
NewFramework.framework. I modify the project for FrameworkA to add a framework reference to '/Marketocracy/Frameworks/NewFramework.framework', and FrameworkA builds just fine without NewFramework.framework being installed, since Xcode
again does it's magic and knows to look in the build products directory for NewFramework.framework.


However, CommandLineTool no longer will link, even though it doesn't actually reference any symbols in NewFramework.framework (it hasn't changed at all from the point where it did work). As far as I can tell, Xcode requires me to add a framework reference to NewFramework.framework in my CommandLineTool project in order for it to link. For some reason, its magic fails it and it doesn't realize to look in my build products directory unless there is an explicit framework reference.

In the 3 project case this isn't too bad, but with 100 projects, it's a real pain to go through them all and add a new framework reference just to be able to build.

Is there an easier way??
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Indirect framework reference problems
      • From: Eric Albert <email@hidden>
  • Prev by Date: Re: Has anyone run a build with xcode and C++ STL on 10.2
  • Next by Date: Re: Do project references work?
  • Previous by thread: RE: Porting XML app from Windows to Mac
  • Next by thread: Re: Indirect framework reference problems
  • Index(es):
    • Date
    • Thread