GEM cribsheet and support files.
On linux or Mac, you can get Gem sources from CVS by typing this to a shell:
cvs -z3 -d:pserver:email@example.com:/cvsroot/pd-gem co Gemor just download this tarball which is the same snapshot I ran from Oct. 9. Then, on linux at least, I was able to compile it as follows:
tar xzf gem-checkout.tgznext cd to gem/Gem/src/Manips and remove all the glsl stuff:
rm glsl_*theoretically, the next things to do should be to "CD" back to "gem/Gem/src" and run "aclocal", "autoconf" then "./configure" with a flag to tell Gem where the Pd source is. This never works as you'd expect. I ended up doing the following:
autoconf ./configure --with-pd=/home/...your-path-here.../pd makemake annoyingly goes back and re-runs the configure script; watch and make sure it remembers about the "--with-pd" flag, which it did last time I tried. Then it goes off and compiles literally hundreds of files and makes the finished library as gem/Gem/src/Gem.pd_linux (probably slightly different on Mac.) Then invoke it, on linux at least, as follows:
...path.../pd/bin/pd -lib ...path.../gem/Gem/src/Gem(note that you don't supply the suffix ".pd_linux" to the Pd command line.)
If anything goes wrong, it seems to work best to start from the beginning.
A surefire way to add a new Gem "pix" object would be to unpack the entire Gem source anew, cd into gem/Sem/src/Pixes, copy one of the sources (a combination of a ".h" and a ".cpp" file) to a new name, go in and search-and-replace all occurences of the object name inside the copied source, then make Gem as above. Gem automatically makes a list of all sources to incude so you don't have to mess with the makefiles at all.
A faster way I haven't tested but which might work would be, after Gem is compiled, copy to a new file, re-run the "./configure" script in source, possibly remove Gem.pd_linux or whatever, and "make".