Trying to understand executable bundle loading
Trying to understand executable bundle loading
- Subject: Trying to understand executable bundle loading
- From: Craig Morris <email@hidden>
- Date: Mon, 07 Aug 2006 20:03:45 -0600
I have a somewhat convoluted situation where I am using RealBasic (as
the interface layer) with calls to a C++ dylib for the grunt stuff.
In turn I would like the dylib to load simple (not CFPlugin) C/C++
plugin bundles which in turn also use some of the dylib's routines. I
use the CFBundle routines to load the bundle and find the bundle
routines and I include the dylib under "External Frameworks and
Libaries" in the bundle project. This all works well as long as I
run in the XCode debugger, but if I try without it, the bundle fails
complaining it can't find the dylib which in fact called it.
Specifically:
error code 4, error number 0 (Library not loaded: /usr/local/lib/
mylib.dylib
If I actually copy mylib.dylib to /usr/local/lib, the program runs
fine, but I suspect it has now loaded two different copies of that
code and I really don't want the dylib to live there.
So finally getting to the question, I am hoping someone might be able
to give me some pointers on how to configure the build of the bundle
so that it will locate the already loaded (by RealBasic) dylib code?
--
Craig Morris
Fernie, B.C., Canada
_______________________________________________
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