• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: statically linking one of my framework to a foundation tool
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: statically linking one of my framework to a foundation tool


  • Subject: Re: statically linking one of my framework to a foundation tool
  • From: Bob Ippolito <email@hidden>
  • Date: Tue, 4 Jan 2005 12:14:58 -0500


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.


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


  • Follow-Ups:
    • Re: statically linking one of my framework to a foundation tool
      • From: Aurélien Hugelé <email@hidden>
References: 
 >statically linking one of my framework to a foundation tool (From: Aurélien Hugelé <email@hidden>)
 >Re: statically linking one of my framework to a foundation tool (From: Nick Zitzmann <email@hidden>)
 >Re: statically linking one of my framework to a foundation tool (From: Aurélien Hugelé <email@hidden>)

  • Prev by Date: Re: NSArray saveToFile: atomically does not work
  • Next by Date: Re: statically linking one of my framework to a foundation tool
  • Previous by thread: Re: statically linking one of my framework to a foundation tool
  • Next by thread: Re: statically linking one of my framework to a foundation tool
  • Index(es):
    • Date
    • Thread