On 31-Jul-07, at 11:48 AM, [EMAIL PROTECTED] wrote: > Alright, so please humor me and reiterate 1,2,3 the procedure for > each OS. > > 1) Mac - debug externally and production in *any* internal folder > (although generally "frameworks").
use @executable_path and put the dylib inside the app package > 2) Linux - ? install the dylib in /usr/local/lib and use a hard coded path to the library > 3) Windows - ? Use an installer and install it in application data/your app name/ library_name.dll Use a hard coded path to it > ...it might not exist, but I'm looking for the most cross-platform > compatible method(s) It doesn't exist because each OS allows you to do different things. OS X is the only one that makes it so an "installer" is really not necessary because all your custom dylibs can be IN the app package which and end user see' and treats as one file. There is no equivalent on Linux or Windows so you have to do things differently They are more similar to each other On Windows you will want an installer so you can put dylibs in the right places and so the end user can remove things later if they desire. On OS X you will want only a DMG if you can do that so it's a drag and drop of the application to install it Linux folks will have to chime in for "what's expected" _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
