Re: can't open library
Re: can't open library
- Subject: Re: can't open library
- From: Francis Derive <email@hidden>
- Date: Tue, 26 Apr 2005 19:02:20 +0200
Bonjour Daniel !
Sorry to be so late, and I can't wait any longer to thank you for your help - which is a real clear work.
I did found it some time ago - the "@excutable_path/../Frameworks" install path which was set in the built settings ( not so cute to do the opposite of what we have learnt in terms of "lexical scoping" - but probably efficient in practice ).
Do you know what ? I have a lot more questions to raise as I practice around, and I don't know where to start !
If you please, only but this one :
In a framework Xcode project I have in hand - OgreKit -, among targets are two frameworks : "OgreKit (Full Set)", and "OgreKit (without Find Panel)". We understand they are variations on the same subject.
After a build - driven by an aggregate target where both above frameworks are there as "Direct Dependencies" - there is only one build "OgreKit.framework" product.
How could that be (only one) ?
For when I add a reference to the project containing this OgreKit framework to a project containing an application, which framework the application will use - as I can add to the application project as a target dependency - one or the other, or even both of the frameworks ?
Francis.
On Apr 10, 2005, at 8:06 AM, daniel wrote:
Aha -- this is exactly what it is. There *is* an internal difference between the frameworks. I didn't realize you were trying to avoid embedding the framework in your app's bundle.
Every framework has embedded in it a "path to itself" ... where it expects to be installed. It looks like whoever built the OgreKit framework chose this for you.
I think there are ways to change it after the fact but the easiest thing might be to see if you can build your own copy of the framework, specifying the INSTALL_PATH build variable as desired for your own purposes.
Somebody else might have better information about this or you might find more by searching for INSTALL_PATH etc.
Daniel
On Apr 7, 2005, at 5:49 AM, Francis Derive wrote:
However, looking at my error message saying "... can't open library: @executable_path/../Frameworks/OgreKit..." - and from what I have superficially retained from the above readings - isn't that message specific of a framework embedding process !
As I have not specified such a process as of my knowing - who could then help at this point ?
It is as if there were an "internal" difference between the two packages OgreKit and OmniFoundation.
_______________________________________________
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