On Fri, Jan 13, 2017 at 6:51 AM, Jma/celeonet jma@jeanmarie-adrien.net wrote:

Sorry to post this again, not sure it went through the first time

What's the way to have two instances of pd, 32 bits (for GEM) and 64 bits (for ram) running in parallel with different binaries / libraries and prefs (OSX) ?

Ans: paths

Easy to do in linux, just compile and install to a non-standard location for each, and when launching add the required libraries to LD_LIBRARY_PATH. To avoid conflicting preference files, I set the HOME variable to a different location for each version of Pd I run (the default preference file is $HOME/.pdsettings on linux).

Maybe you have some way to install one package, move it to a new directory, and then install the 2nd one? look for any hardcoded paths in the application folder, if something breaks

1- Where is the smart place for externals / libraries so that they do not conflict : is it possible to stick them anywhere, has it to be in /Lib/Pd or can they be in the application packet for the 64bits the old way ? (I'm looking for the professional way before hacking around)

well, I'd encourage you to just hack around :) . There might be some good way to modify your app bundle so each app just uses the libraries installed and doesn't touch the other application's libraries. Then, you could launch them from the icon.

Otherwise, you have to start them in the terminal, and you will purposely want to keep your standard locations for libs (like /Lib/Pd) empty of libraries that may conflict. Then, in the terminal you can use the DYLD_LIBRARY_PATH variable to add any path locations for the linked libraries, and start pd on the command line. Any externals are dynamically loaded and only need to be in pd's search path (which is why you probably want the preference files separated as well)

2- Is there a way to have specific prefs for the 64bits in the default file inside app packet, and no prefs in the /Usr/Library/Préférences ? (Same note).

Tks

JmAdrien