Internal Framework linked from an internal helper app
Internal Framework linked from an internal helper app
- Subject: Internal Framework linked from an internal helper app
- From: Eric Roccasecca <email@hidden>
- Date: Thu, 11 Mar 2004 16:51:24 -0600
The app I am working on has the following (simplified) layout:
MyProgram.app
Contents
MacOS
MyProgram
Frameworks
MyFramework.framework
PlugIns
OneOfMyPlugins.plugin
Resources
HelperProgram.app
MyProgram links to my internal framework MyFramework and my plugins,
which are loaded into MyProgram, link to this same framework. This of
course works fine because in my framework the "Installation Path" is
set to "@executable_path/../Frameworks". Straight forward stuff, well
once I understood it a couple years ago.
The problem is that now I am needing to use MyFramework from inside
HelperProgram. Well since that is a different memory space at runtime
it doesn't have the advantage of having the framework already loaded at
runtime like the plugins do in the main application (MyProgram). So
MyFramework needs to be loaded into my HelperProgram. The problem is
the install path of MyFramework in HelperProgram is not correct. The
framework is not inside the helper, but is actually a sibling in a
sense to the helper so the library is not found at runtime and bad
things happen.
I took at look at "ld" to see if I could use some "Other linker flags"
in Xcode to fix this when HelperProgram is compiled. Some of the flags
looked promising (-dylib_file, -executable_path), but they did not
actually provide any benefit (or maybe I didn't use them correctly).
So anyone know how to handle this situation? Some utility to run after
the fact? Some param to change somewhere? Thanks ahead of time.
--Eric
Eric Roccasecca
Lead Macintosh Software Engineer
CE Software, Inc.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.