Re: Building framework with another framework
Re: Building framework with another framework
- Subject: Re: Building framework with another framework
- From: Steve Mills <email@hidden>
- Date: Mon, 7 Jan 2008 15:19:50 -0600
(Sending to list. First went to Ryan only.)
On Jan 7, 2008, at 12:52:58, Ryan Homer wrote:
• Yes you are supposed to type @executable_path exactly like that;
it will be replaced by the dynamic library loader at runtime.
• If your .h file is not copying over, it might be set as type
"Project" and not as "Public".
Ah. That hidden setting has bitten me before. I don't know why they
don't put it in plain view in the Get Info window where everything
else is, rather than only in the contextual menu for the file. Unless
I'm just not seeing it in some other more obvious location.
• In some cases, you do indeed want to look for your libraries in
@executable_path/Frameworks, but in other cases, you need to check
in @executable_path/Frameworks/CCILib.framework/Versions/Current/
Frameworks in order to find the MAAEL.framework. You may need to
create a soft link from the first Frameworks directory so that
MAAEL.framework also appears to be a sub-directory of it.
• I notice that one of the errors is "@executable_path/../
Frameworks/MAAEL.framework/Versions/A/MAAEL" which seems to confirm
#3.
Hmm, can you explain in more detail what you mean? Pretend you're
explaining it to a newbie please.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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