Re: How to use a framework in a non-standard location?
Re: How to use a framework in a non-standard location?
- Subject: Re: How to use a framework in a non-standard location?
- From: Andy Wiese <email@hidden>
- Date: Tue, 23 Nov 2004 04:20:57 -0600
On Nov 23, 2004, at 2:24 AM, j o a r wrote:
Did you follow the instructions for creating an embedded framework?
<http://developer.apple.com/documentation/MacOSX/Conceptual/
BPFrameworks/Tasks/CreatingFrameworks.html#//apple_ref/doc/uid/
20002258/BAJJBIEF>
j o a r
I tried to. But you prompted me to try a little harder. Thanks.
I gather from this that INSTALL_PATH is actually a value stored
somewhere inside the framework that tells the dynamic linker where to
go looking for the framework at runtime? The instructions seemed
obsolete and I really just thought it was the build destination.
So are there some default locations that are always searched even if
the framework is not at the INSTALL_PATH? That would explain why the
application would run if it was in the same directory as the framework.
On 2004-11-23, at 09.08, Andy Wiese wrote:
My question is how to build an external test application to use a
framework without having to install the framework in a default
location?
I have built a framework. It currently just builds into its project
build directory.
I have another target that builds a test app into the same build
directory. It finds the framework and runs just fine.
I have another project that builds a similar test application. I
dropped the framework into the Frameworks and Libraries Build Phase,
and I have a Framework Search path in the target build settings to
the framework. (I think the path was put there automatically? I don't
remember entering this setting). It builds and links, but at launch
it gives me this error:
dyld:
/Users/andy/Projects/xcode_sandbox/m_/m_demo/build/m_demo.app/
Contents/MacOS/m_demo can't open library:
/Users/andy/Library/Frameworks/m_core.framework/Versions/A/m_core
(No such file or directory, errno = 2)
Based on recommendation in the (probably obsolete) Introduction to
Mac OS X Frameworks documentation, I put a Copy Files build phase in
and copied the framework to the Frameworks directory of the
application bundle. I confirmed that it is copied ok.
I clean, rebuild and launch, and get the same error exactly.
I copied the framework into the ~/Library/Frameworks folder, where
dyld seems to be looking for it, and everything runs just fine.
During development, it seems too inconvenient to have to copy the
framework to some default shared location. Also for development
demos, it would be great to package the framework inside the demo
app. Can anyone help me with the secret handshake to make this work?
_______________________________________________
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