• 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: Framework issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework issues


  • Subject: Re: Framework issues
  • From: Andreas Grosam <email@hidden>
  • Date: Wed, 23 Mar 2005 11:00:08 +0100


On 22.03.2005, at 22:32, Scott Tooker wrote:

Hmm, can you post the errors that you are getting when building? From your description below it's not clear exactly what is wrong.

Also, don't put third party frameworks in /System/Library/Frameworks. /System is meant for Apple frameworks and the like (the sole exception being kernel extensions). 3rd party frameworks should be installed in /Library/Frameworks/. If you are developing a new framework that you want other proejcts to access, you can share a build products directory among the projects or place the framework in ~/Library/Frameworks (the latter option means that only your user account will use the framework).

Scott


Just yesterday i attempted to use a third party framework . The linker ld will fail to link sub-libraries from third party *umbrella* frameworks when they are not located in /Library/Frameworks - no matter what you try to specify in the options.

For further details: i already posted a msg in this list: "XCode does not find libraries in an umbrealla framework".

IMO, XCode could be improved much regarding the handling of frameworks. For instance, why does it not automatically generate the required -F options through using the infos from the project? When adding a framework to the project, all required info is already there, no need for explicitly specifying the framework path! But XCode forces us to do this.

Andreas

On Mar 22, 2005, at 11:30 AM, Phil Ershler wrote:

I am working on a couple of fairly simple projects that need access to the FWLib.framework. I have installed the latest FireWire SDK. It has an example project that builds the FWLib.framework. I have built that framework and copied it to /System/Library/Frameworks. Now I have two projects that both use the FWLib.framework. One of the projects builds just swell. The other project gets into a series of cascading errors (over 200) when I try to reference the same framework. The errors begin with a namespace FWLib statement in one of the include files that makes up the framework. I have deleted the framework from both projects and re-added it to both projects so that I believe I am referencing the same framework in both projects. After cleaning both projects and trying to rebuild, the one project rebuilds as before and the other project fails in the same way as above. What am I missing?

Thanks, Phil Ershler

_______________________________________________
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


_______________________________________________
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

 _______________________________________________
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: 
 >Framework issues (From: Phil Ershler <email@hidden>)
 >Re: Framework issues (From: Scott Tooker <email@hidden>)

  • Prev by Date: Re: problem after reinstalling xcode 1.5!
  • Next by Date: worth it to target 10.1?
  • Previous by thread: Re: Framework issues
  • Next by thread: Adding Library
  • Index(es):
    • Date
    • Thread