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:19:24 +0100
great ! i''l try that :)
thanks for your help !
On 4 janv. 05, at 18:16, Brendan Younger wrote:
On Jan 4, 2005, at 11:01 AM, 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 ..
There are three different ways to create a library on Mac OS X: a
framework, a dynamic library (has extension .dyld), and a static
library (has extension .a). The previous poster was referring to
dynamically linked libraries (.dyld). What you want to do is create a
new target in your framework project in Xcode and choose the target
type "static library". Then add all your framework code to the static
library target and build a static library with extension ".a". Add
the static library to the project for your foundation tool and
everything should work.
Brendan Younger
_______________________________________________
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