Re: More on embedding frameworks
Re: More on embedding frameworks
- Subject: Re: More on embedding frameworks
- From: Randall Meadows <email@hidden>
- Date: Tue, 17 Jul 2007 11:37:05 -0600
OK, so I've seen the error of my ways (thanks Brian!), and I'm
abandoning efforts to embed my frameworks in my app bundle (at least
for the Debug config). I have all my frameworks now ending up in
/Users/randy/Library/Frameworks/, and my app runs superbly.
I'm now trying to build a custom IB palette, which depends on two of
these frameworks. Actually, this project has two targets: one is a
framework, DynamicUI.framework which depends on two other frameworks;
the 2nd is the IB palette target, which depends on the
DynamicUI.framework from the other target.
When I link the palette target, during the link I get two warnings of the sort:
"warning can't open dynamic library:
/Developer/SDKs/MacOS10.4u.sdk/Users/randy/Library/Frameworks/DevUtils.framework/Version/A/DevUtils
referenced from:
/RC8-fix-fmwks/Frameworks/DynamicUI/../../build/Debug/DynamicUI.framework/DynamicUI"
I don't get why it's tacking $SDKROOT onto the front of the framework path.
This results in 2 undefined symbols, since it can't find the two frameworks.
Only instance of "/Developer/SDKs/MacOS10.4u.sdk" in the project
settings is the definition of SDKROOT.
I've used 'otool -LD' to look inside the involved frameworks, and
everything looks OK.
I've perused the build transcript; "/Developer/SDKs/MacOS10.4u.sdk"
appears in each gcc invocation as "-isysroot
/Developer/SDKs/MacOS10.4u.sdk", in all the compiles and in the link;
that's it.
randy
_______________________________________________
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