• 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: Fw: GetSharedLibrary
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fw: GetSharedLibrary


  • Subject: Re: Fw: GetSharedLibrary
  • From: Chris Reed <email@hidden>
  • Date: Fri, 4 Jul 2003 22:26:34 -0500

The correct way to deal with external shared libraries that are part of your product is this:

1. Put the libraries in your bundle. Please. Do not put them somewhere else, unless they are user manageable plug-ins. If you don't believe me, then please at least put them in ./Library/Application Support/Your_ Company_Name
2. Use NSBundle or CFBundle to construct the path to the shared library. If you decide to put your library outside of the bundle, use FSFindFolder to to locate the Application Support directory.
3. Use GetDiskFragment to load a CFM shared library--this is preferred to GetSharedLibrary. For one thing, you know for sure which library will be loaded. It takes an FSSpec, so you'll have to convert the path to an FSRef using CFURL and then an FSSpec using FSGetCatalogInfo.

-chris

On Friday, Jul 4, 2003, at 15:46 US/Central, Michael Olsen wrote:

Any ideas on how to do it properly?

Put all your resources into your app's bundle. NSBundle has fine
methods to get the absolute paths independant of how you start your app.

That won't do, I'll still need the path for misc. things like preferences etc. etc.

Spraying around libraries and resources in various locations on the
platter is kind of depreceated on Mac OS. Mac Users don't like
installers, want to do Drag & Drop install and want to test your app
without installing it at all, i.e. they want to launch it off the
CD/Disk Image.

Hope that helps your understanding of the Mac way of computing.

Hmm, yes, but my primary concern is to deliver the software for x number of platforms (it's an audio plug-in) as fast as possible, and the best way, in my opinion, to do this is to have all the core inside a shared library.


Greets,

Michael Olsen
email@hidden




... who unfortunately has to do osx work I would say ;)

Ah, you're kidding ;-)


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Fw: GetSharedLibrary (From: "Michael Olsen" <email@hidden>)

  • Prev by Date: MIDI problem, can I determin the MIDI source is vertual or phisycal?
  • Next by Date: Re: Fw: GetSharedLibrary
  • Previous by thread: Re: Fw: GetSharedLibrary
  • Next by thread: Re: Fw: GetSharedLibrary
  • Index(es):
    • Date
    • Thread