Hi everyone,
I've noticed that when compiling pix_externals in the extra folder it creates an "alias" for pix_external.pd_darwin (or _linux if that is the case). Therefore this file cannot be put in a folder inside a project and declared with [declare -path].
Does GEM create such a file? and where does it put it?
best,
J
On 11/15/2012 03:47 PM, J Oliver wrote:
Hi everyone,
I've noticed that when compiling pix_externals in the extra folder it creates an "alias" for pix_external.pd_darwin (or _linux if that is the case). Therefore this file cannot be put in a folder inside a project and declared with [declare -path].
i guess by "alias" you mean a "symlink" (on systems that support it).
Does GEM create such a file? and where does it put it?
yes. libtool (which Gem uses to build externals) will create the actual binary files in a hidden folder .libs/; only when you install the library (using "make install"), they are put into the correct place.
this is a bit impractical when developing code, so Gem creates some symlinks to outside of .libs (e.g. pix_foo.pd_linux -> .libs/pix_foo.pd_linux)
if you want to distribute the binaries, the simplest way is to do an installation to some dummy place, e.g. $ make install extradir=~/Desktop/pix_foo
or more generic (non Gem-specific) $ make install DESTDIR=/tmp/bar $ cd /tmp/foo $ ls
fgmdst IOhannes