[PD-dev] installation paths

[d.lj]

i think settling on PDDIR is a good start.

autoconf for the nearer future.

re: libraries: there's a misunderstanding since i was thinking of
libraries as in liblame.so etc and not as in OSC.pd_linux

but still, having 500 single files in the externs dir is a bit messy
too when you only have, say, 10 packages installed. for large packages
libraries kind of do make sense but anyway ..

re name-clashes: if there are clashes, one install will just overwrite
an older install of an object of the same name, so you ll still have to
start searching which overwrote what. only after you found it, its
easier to choose which one you want to use.

ynk,j

[Frank Barknecht]->[Re: [PD-dev] installation paths]->[04-02-02 16:33]

 |Well, maybe policy is a too strong word. As I am a Makefile and
 |autoconf idiot, I am a prime example of those copy and paste guys: I
 |just use the same system, that Thomas uses in the flext-tutorials.
 |(I would love to see an autoconf example for flext exernals. I will
 |adapt it immediatly.)
 |
 |If everyone was using autoconf, we would have no problems. It gets
 |difficult, when Makefiles are using DESTDIR, PDDIR or whatever as
 |install target. Yes, if you compile everything separately, this is
 |fine: just look into the Makefile, search for install and edit it. But
 |this is tedious work, so an agreement on, say, using PDDIR as install
 |path would help a lot.
 |
 |Oh: And I don't want to forbid libraries, but they will have to be
 |dealt with differently than single externals and they are more prone
 |to carry undiscovered name clashes.
 |
 |ciao
 |

-- 
>          <          D          u          .          o          r          g
GPG-key at http://xdv.org/~jdl/jdl.pub.asc