[PD] help compiling recent GEM

IOhannes m zmoelnig zmoelnig at iem.at
Thu Sep 18 09:59:28 CEST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2014-09-16 17:47, mick mengucci wrote:
> Here's my feedback:

thanks

> the $ pd -path ./abstractions:. commando worked fine! I open the pd
> in the directory where I downloaded and installed the recent
> version of GEM, and it basically works fine. [gemwin] and vlc
> plugin are there and alive.

cool.

> 
> I just to want to add a couple of notes: 1) when I feed [pix_video]
> with a stream created in vlc on another laptop I get the image but
> with the channels R and B inverted! This does not happen when I
> stream from my laptop to one of my collegue (he gets the correct 
> colors).

this sounds very much like a bug that has been reported as
  https://github.com/umlaeute/Gem/issues/56
and which i have fixed in commit 7eb6c057 (11th september).

is your checkout recent enough?


> 2) About the $ make install I had already used that command (as I
> followed the instructions on the above mentioned site). Should I do
> it again?

once (after a successfull build) should be enough.

after doing "make install" you will have to use the path you installed
to (rather than the path where you built Gem).

e.g.
$ mkdir -p ~/src/
$ cd ~/src
$ git clone https://github.com/umlaeute/Gem.git
$ cd Gem
$ ./autogen.sh && ./configure

$ make install DESTDIR=/tmp/Gem

$ cd ~

$ pd -path /tmp/Gem/usr/local/lib/pd/extra -lib Gem


so this boils down to:
"make install" will assemble everything to run Gem in a single
directory "somewhere else" (by default this is
/usr/local/lib/pd/extra), but is settable, e.g. with the DESTDIR variable.

it does not magically turn your build-tree into a usable (as in
"out-of-the-box") setup for running Gem.

if you have changed anything that involves recompilation, you have to
do "make install" again.


> My friend suggests that some eror might have occured when compiling
> the new GEM and I might have some libraries not correctly
> assigned.


if the build fails for whatever reason (e.g. when building some plugin
you are not interested in anyhow), the "make instalL" will also fail,
and also some convenience symlinks that allow you to use the "-path
abstractions:." trick.
since the latter seems to work for you, i don't think that this is the
problem here.


fgamsdr
IOhannes


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUGpDdAAoJELZQGcR/ejb4PHcQAIXpFz2zcnePiXqw4bhSsvhL
zydm4Mbi/lhmx2ZOk0Xt45m9pSF08HUZu07a6WxZeJVV+oRSqDSWLVXs0i7Qdlqb
4sjXLb0eQLzef7NuEvVbtVDDhUgCR0CqpOy2RN0TOJp8jkBhZaTcPpv6pueMb7ze
wjfvQ5/c1USQvFKA8hJUYVVK+fxWnYF2KSnFnUki1Z6+/O43RYEjmZQxTNoqK6X0
EPQcheznsDz/SJet187W/bpK/Epn14cOQO+AHdsUzfKJd5BKk80iKPgB0BakcYeL
X3yoQyJsCTRY2kn7XZT6IRkbVreBp70NUd9cWp6KV2iugoCpEwFMZzd7wGSkLTvu
fVpAOGqgf0TASrOhja6grjRNFsN+tQbXlN2j00whpe0hhkjKFP/wEaBby0M0DQ94
4aUVMLGtss0Sd234XAX++OPo2Q4XWUeydFaD+ABvxwGmntEISBxLSaX1OZJf38ut
q6hjYsPWbxSZJQuJUHEVrCImRdJXMjse9t+yxvzS8Nd7U9DoglwvF1FSkWomXsFm
Rgup3fL/ao0J8ZTQBkFVjQjuFwio0E2kYS42b8fHytLkuKUjDH4bNYs+eu9KlR8I
M/iWpNRS+VZPdJ3UE/CwuLHpHR6Y8K3KhYylZ2uSGvK+lWRj/hJAXO2UrZU5+rDc
BQWCQPpaqUtYwSmqmebQ
=5G3J
-----END PGP SIGNATURE-----



More information about the Pd-list mailing list