Re: statically linking one of my framework to a foundation tool
Re: statically linking one of my framework to a foundation tool
- Subject: Re: statically linking one of my framework to a foundation tool
- From: Aurélien Hugelé <email@hidden>
- Date: Tue, 4 Jan 2005 18:23:59 +0100
On 4 janv. 05, at 18:14, Bob Ippolito wrote:
On Jan 4, 2005, at 12:01 PM, Aurélien Hugelé wrote:
On 4 janv. 05, at 17:54, Nick Zitzmann wrote:
On Jan 4, 2005, at 9:39 AM, Aurélien Hugelé wrote:
now i have another project, that would need linking one of my
framework to a *foundation tool* (so no framework is not
embeddable). I need static linking (As i understand ...)
can this be done ?
No; you can't statically link something to a dynamic library, and I
don't think there is a way to create a static framework. (You can
create a static library, but not a static framework.) What you might
want to do instead is consider
excuse me for my ignorance but i don't understand why you call a
foundation tool, a dynamic library ...
A framework is a dynamic library (MH_DYLIB). Presumably, he was not
referring to the executable.
relocating your framework to a standard path, e.g.
/Library/Frameworks, and using it from there. You shouldn't need to
change the framework's installation path to do this; if you put a
framework into /Library/Frameworks, the linker will probably find it
without any problems.
yes this works, but installing frameworks to this location requires
(i think) a package with an installer (which i often hate :-( )
So does installing a "foundation tool" to /usr/local/bin. What's your
point? If you plan on distributing via DarwinPorts or Fink then they
have suitable mechanisms for installing such stuff.
in fact it is because my project is divided in two parts :
a daemon (this is the foundation tool) and an application (normal
NSApplication bundle)
the deamon needs a link to my framework whereas my application does not
(it is simply a GUI for the daemon)
what would you do it this case ?
Another alternative is to simply use an application bundle, and create
a symlink or shell script wrapper for convenience that calls into your
application bundle, then you get the encapsulation and you can use
@executable_path style load commands.
-bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden