[Gridflow-dev] make install
matju at artengine.ca
Sun Jan 15 00:57:00 EST 2006
On Sun, 15 Jan 2006, Alexandre Castonguay wrote:
> Le Samedi 14 Janvier 2006 00:10, Mathieu Bouchard a écrit :
> > let's have GF be compiled and run in the same
> > place, in lib/pd/extra/gridflow, what do you say?
> I don't know matju, what does it change?
Well, I was thinking about a few things:
1. don't install ruby files in the ruby directories because ruby users
don't care about gridflow and because it's less troublesome to keep
everything in the Pd side.
2. if (1) is done, then we may as well not install anything at all.
However this means setting a -path to GridFlow's abstractions because
they won't get copied straight to lib/pd/extra; this might be better
because it makes GridFlow easier to uninstall... and arguably, to
install (hehehe). However gridflow.pd_linux has to figure out its own
location so that it can find the rest of GridFlow. It would put that
dir in the RUBYLIB envvar (which is the equivalent of LD_LIBRARY_PATH
but for *.rb files).
A nice advantage of (2) is that abstractions can be edited by right-click
"Open", saved, and then cvs commit, without having to worry about copying
them back to the original directory, and not having them overwritten by
the next "make install".
3. as an alternative to (1), GridFlow might bundle Ruby. This also
requires gridflow.pd_linux to figure its own location so that it can
find libruby.so, but it doesn't exclude a "make install" procedure.
4. Ideally I'd like to have the choice, either (1) and (2) together, or
(3), but in any case, I'd ditch "make install". (I don't particularly
believe in UNIX conventions anymore...)
_ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montréal QC Canada
More information about the Gridflow-dev