Re: Embedding frameworks across projects
Re: Embedding frameworks across projects
- Subject: Re: Embedding frameworks across projects
- From: Adrian Sampson <email@hidden>
- Date: Sat, 4 Mar 2006 18:40:44 -0800
Thank you both for your help.
Are you using a shared built products directory for both projects? I
think that might be a requirement for this kind of thing to work.
Great advice. I probably should have been doing this anyway -- this
way, Xcode can't help but find the framework.
I could be going about this all wrong, though. I have changed the
build paths in both the framework and application projects to a
single directory (I didn't change my global Xcode preferences so that
these projects might compile in other environments). Now, however,
Xcode passes an -F parameter to gcc indicating the (nonexistent)
build folder of the framework project. The warning, predictably, is
this:
warning -F: directory name (/Users/adrian/FRAMEWORK_PROJECT_PATH/
build/Debug) does not exist
(I guess what I've learned from all this is that Xcode doesn't
actually look at the build path of the referenced project. When using
gcc, it just passes a reasonable coverage of paths: (1) the Xcode-
global default build path for the referenced product (ie, the
framework) and (2) the build path for the referencing project (ie,
the application).)
It is.
http://www.cocoabuilder.com/archive/message/cocoa/2000/10/13/32941
Also the framework search path that is wrong is in your framework
and not
your project. Click on the framework target and select build
settings tab
look for Installation Directory.
I think I have this correct: I've set the installation path of the
framework to "@executable_path/../Frameworks". Is this what you meant?
Thanks again,
- Adrian
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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