doh...this mua drives me crazy
mfg.hdt.kfs IOhannes
...sent from my pdp-11...
-------- Ursprüngliche Nachricht -------- Von: IOhannes m zmölnig zmoelnig@iem.at Datum:2014.08.20 20:56 (GMT+01:00) An: Nicolas Montgermont nicolas_montgermont@yahoo.fr Betreff: AW: Re: [GEM-dev] gemwin
I think all problems you are seeing are because the source tree is not the preferred way of using gem. the preferred way is: make install
this will put all Gem things (binaries, abstractions, plugins) into a single directory: .../extra/Gem/
loading Gem will automatically add this path to Pd's search path, so a single [declare -lib Gem] should be enough.
mfg.fhd.ite IOhannes
hello,
yes, you are right, make install copy the gemwin abstraction in the correct place.
but still, loading Gem (with pd -lib Gem, or with declare -lib Gem) did not work.
in fact it search for : ... tried /usr/local/lib/pd/extra/gemwin.pd and failed ...
but it is on /usr/local/lib/pd/extra/Gem/gemwin.pd
c
Le 20/08/2014 21:03, IOhannes m zmölnig a écrit :
doh...this mua drives me crazy
mfg.hdt.kfs IOhannes
...sent from my pdp-11...
-------- Ursprüngliche Nachricht -------- Von: IOhannes m zmölnig Datum:2014.08.20 20:56 (GMT+01:00) An: Nicolas Montgermont Betreff: AW: Re: [GEM-dev] gemwin
I think all problems you are seeing are because the source tree is not the preferred way of using gem. the preferred way is: make install
this will put all Gem things (binaries, abstractions, plugins) into a single directory: .../extra/Gem/
loading Gem will automatically add this path to Pd's search path, so a single [declare -lib Gem] should be enough.
mfg.fhd.ite IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
On 20. August 2014 21:18:19 MESZ, Cyrille Henry ch@chnry.net wrote:
hello,
yes, you are right, make install copy the gemwin abstraction in the correct place.
but still, loading Gem (with pd -lib Gem, or with declare -lib Gem) did not work.
in fact it search for : ... tried /usr/local/lib/pd/extra/gemwin.pd and failed ...
but it is on /usr/local/lib/pd/extra/Gem/gemwin.pd
This is where it should be. If it's not found,then this is a bug...
mfg.dgs.IOhannes
When i make install, it tries to copy into: /usr/local/lib/pd/extra/Gem/ but on osx, it should stand in ~/Library/Pd/Gem/
n
Le 20/08/2014 21:03, IOhannes m zmölnig a écrit :
I think all problems you are seeing are because the source tree is not the preferred way of using gem. the preferred way is: make install
this will put all Gem things (binaries, abstractions, plugins) into a single directory: .../extra/Gem/
loading Gem will automatically add this path to Pd's search path, so a single [declare -lib Gem] should be enough.
mfg.fhd.ite IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
On 20. August 2014 21:55:01 MESZ, Nicolas Montgermont nicolas_montgermont@yahoo.fr wrote:
When i make install, it tries to copy into: /usr/local/lib/pd/extra/Gem/ but on osx, it should stand in ~/Library/Pd/Gem/
You can configure that when calling 'make install'
how can I do that? running make install DESTDIR=/Users/nix/Library/Pd/ creates me: /Users/nix/Library/Pd/usr/local/lib[...]
thx in advance! n
Le 20/08/2014 22:01, IOhannes m zmölnig a écrit :
On 20. August 2014 21:55:01 MESZ, Nicolas Montgermont nicolas_montgermont@yahoo.fr wrote:
When i make install, it tries to copy into: /usr/local/lib/pd/extra/Gem/ but on osx, it should stand in ~/Library/Pd/Gem/
You can configure that when calling 'make install'
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-08-20 23:31, Nicolas Montgermont wrote:
how can I do that? running make install DESTDIR=/Users/nix/Library/Pd/ creates me: /Users/nix/Library/Pd/usr/local/lib[...]
yes, that's right, use "libdir" (i know it's nowhere documented).
the following should install into /Users/nix/Library/Pd/Gem (and /Users/nix/Library/Pd/pix_mano,....):
$ make install libdir=/Users/nix/Library/Pd/
it will probably still give you an error, as it will try to install some dev-files (headers, pkgconfig) into /usr/local/ and might not have the appropriate permissions. you can either ignore that (add the "-k" flag to make), or use something like $ DEST=/Users/nix/Library/Pd/ $ make install libdir=${DEST} prefix=${DEST}/Gem/stuff
which will put all the additional stuff into /Users/nix/Library/Pd/Gem/stuff.
the reason why this is so complicated is, that the so produced binaries are not well distributable anyhow (at least if you want to make sure that the various plugins work for people who don't want to install a large number of packages).
my way (iirc, it's been a long time) to create the "installer" packages for OSX systems is something like: $ [...] $ make install DESTDIR=/tmp/foo $ mkdir /tmp/Gem $ cp -rav /tmp/foo/usr/local/lib/pd/extra/Gem/* /tmp/Gem/ $ cp -rav /tmp/foo/usr/local/include/Gem /tmp/Gem/ $ cp ${ALL_DEPENDENCIES} /tmp/Gem/ $ for i in /tmp/Gem/*.so; do script-to-make-deps-local ${i}; done $ ./build/osx-dmginstaller/buildinstaller.sh /tmp/Gem/
fgmsdar IOhannes
Le 21/08/2014 09:53, IOhannes m zmoelnig a écrit :
it will probably still give you an error, as it will try to install some dev-files (headers, pkgconfig) into /usr/local/ and might not have the appropriate permissions. you can either ignore that (add the "-k" flag to make), or use something like $ DEST=/Users/nix/Library/Pd/ $ make install libdir=${DEST} prefix=${DEST}/Gem/stuff
which will put all the additional stuff into /Users/nix/Library/Pd/Gem/stuff.
that's working well
the reason why this is so complicated is, that the so produced binaries are not well distributable anyhow (at least if you want to make sure that the various plugins work for people who don't want to install a large number of packages).
my way (iirc, it's been a long time) to create the "installer" packages for OSX systems is something like: $ [...] $ make install DESTDIR=/tmp/foo $ mkdir /tmp/Gem $ cp -rav /tmp/foo/usr/local/lib/pd/extra/Gem/* /tmp/Gem/ $ cp -rav /tmp/foo/usr/local/include/Gem /tmp/Gem/ $ cp ${ALL_DEPENDENCIES} /tmp/Gem/ $ for i in /tmp/Gem/*.so; do script-to-make-deps-local ${i}; done $ ./build/osx-dmginstaller/buildinstaller.sh /tmp/Gem/
yes I remember making a script like that to install dev gem *inside* pd-extended a few years ago, if you want to have a look: http://www.nimon.org/tmp/install_pdx.sh
thanks n
my way (iirc, it's been a long time) to create the "installer" packages for OSX systems is something like: $ [...] $ make install DESTDIR=/tmp/foo $ mkdir /tmp/Gem $ cp -rav /tmp/foo/usr/local/lib/pd/extra/Gem/* /tmp/Gem/ $ cp -rav /tmp/foo/usr/local/include/Gem /tmp/Gem/ $ cp ${ALL_DEPENDENCIES} /tmp/Gem/ $ for i in /tmp/Gem/*.so; do script-to-make-deps-local ${i}; done $ ./build/osx-dmginstaller/buildinstaller.sh /tmp/Gem/
maybe we could add this explanation to the wiki page [1] ? but does the `script-to-make-deps-local` exists in Gem ? there is such a script made by Hans in `pix_opencv` repo [2].
+ a
[1] : https://github.com/umlaeute/Gem/wiki/How-to-build-Gem-on-MacOSX-Mavericks [2] : https://github.com/avilleret/pix_opencv/blob/master/embed-MacOSX-dependencie...
$ make install libdir=/Users/nix/Library/Pd/
is there a reason this is not automatic when osx is detected as os with ./configure?
On Thu, Aug 21, 2014 at 3:53 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-08-20 23:31, Nicolas Montgermont wrote:
how can I do that? running make install DESTDIR=/Users/nix/Library/Pd/ creates me: /Users/nix/Library/Pd/usr/local/lib[...]
yes, that's right, use "libdir" (i know it's nowhere documented).
the following should install into /Users/nix/Library/Pd/Gem (and /Users/nix/Library/Pd/pix_mano,....):
$ make install libdir=/Users/nix/Library/Pd/
it will probably still give you an error, as it will try to install some dev-files (headers, pkgconfig) into /usr/local/ and might not have the appropriate permissions. you can either ignore that (add the "-k" flag to make), or use something like $ DEST=/Users/nix/Library/Pd/ $ make install libdir=${DEST} prefix=${DEST}/Gem/stuff
which will put all the additional stuff into /Users/nix/Library/Pd/Gem/stuff.
the reason why this is so complicated is, that the so produced binaries are not well distributable anyhow (at least if you want to make sure that the various plugins work for people who don't want to install a large number of packages).
my way (iirc, it's been a long time) to create the "installer" packages for OSX systems is something like: $ [...] $ make install DESTDIR=/tmp/foo $ mkdir /tmp/Gem $ cp -rav /tmp/foo/usr/local/lib/pd/extra/Gem/* /tmp/Gem/ $ cp -rav /tmp/foo/usr/local/include/Gem /tmp/Gem/ $ cp ${ALL_DEPENDENCIES} /tmp/Gem/ $ for i in /tmp/Gem/*.so; do script-to-make-deps-local ${i}; done $ ./build/osx-dmginstaller/buildinstaller.sh /tmp/Gem/
fgmsdar IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQIbBAEBCAAGBQJT9aV/AAoJELZQGcR/ejb4fdMP93UBO4ZCrD4SLUmRuc4vKxb/ MKe0wtdCa1ZNj+Xsk6xLV5/o2CIyOMZX+kAhQLGI7MfhJMAN6NlBkEeOKhQc1IKT ojsAIm0AneCt4wi/CywHr6bcapJjAuiSQ/rFOtwFJ0I/1X/7OOXcBoZLU+bzErR1 TVheKtoNYTPiR2DZ/qcKbXdzP25O5zMvOXGozpkDVvS3V9OvlXV+qxgpR3OxdrNm OCiVNbijpSAmIpJY2WI0ZqFmIDl3uddUeaIkI0WboCAwjEjOhYL+qcyXc+0Zjz/S jZ+lLa1PuQhIblW5AtY1QjjbEDKMjVfFu9wDIVJf2Jr7LMolceCGIq/j6hbpEpSX hUvGHJlMT8F9GWWZ+1VDdnILmrng1LCWJcJ0WjtjH16w0PUWEwHzgYNCBOtkNskO S6ORYbPi11f2+i1Py5ZbWsda5/Nmn2vhE9f5zNWjy8eLXeAuCpkbjmrLNGikw9hf ILb+eEIRhdZ933C4fh90brkEKJ7dAa889aWLHg4WQBL4tcBSYP942nCUUIS4s3Wp BaDnMbj9Y+DvxYs7XM8EaLzAWAN7sq3WXaV0JOx8aqIp1AC8FppbXXtjZAz9brmQ vbhh6L5yJM9axh9cUK7WQ/qVkXnYd6XiVspYJQkHb8O6TASIBuR5url8izM9WahL wf1Vl+uB/GPQyWMdKks= =VfYl -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
On 21. August 2014 18:25:42 MESZ, "me.grimm" megrimm@gmail.com wrote:
$ make install libdir=/Users/nix/Library/Pd/
is there a reason this is not automatic when osx is detected as os with ./configure?
mainly because i considered the usecase non-important.
Most osx (and w32) users do not compile. And the installation packages are/canbe handmade.