[PD-dev] how to load shared code for libraries

[Hans-Christoph Steiner]

That's a good break down of the issues.  I'll checkout @loader_path.   
The @executable_path technique has been in Pd-extended for a long  
time, check out all of the libs in Pd-extended.app/Contents/lib by  
doing something like:

otool -L /Applications/Pd-extended.app/Contents/lib/libavcodec.51.dylib

But this still leaves us with Windows and GNU/Linux, right?  I think  
the original idea of setting the LD_LIBRARY_PATH when loading, then  
unsetting, is a good one.  It would be good to have all platforms use  
the same technique.

.hc


On Sep 27, 2011, at 3:42 AM, IOhannes m zmoelnig wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> http://cocoaconvert.net/2009/08/02/frameworks-with-private-frameworks/
>
>>
>> fgmasdr
>> IOhannes
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk6BflIACgkQkX2Xpv6ydvSK+gCgqhyxJVkNuR8hjsB4NWfGnmgi
> QXgAoMrmStRdLgq/WGf6XVgUSWBXa6BP
> =9UUb
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev



----------------------------------------------------------------------------

"Making boring techno music is really easy with modern tools, but with  
live coding, boring techno is much harder." - Chris McCormick