LD_LIBRARY_PATH vs KAFFE_LIB

[Alexandre Oliva]

Pavel Roskin <Pavel.Roskin at ecsoft.co.uk> writes:

> Is it not better to use another name, for example KAFFE_LIB and
> define it as LIBRARYPATH in external.h for all OS'es?

That would be a good idea, if kaffe would merge KAFFE_LIB and
LD_LIBRARY_PATH to form its internal library path.  Using a definition
from setting LD_LIBRARY_PATH is the expected behavior for most Java
programmers that have had to work with native code, though, so IMO
keeping LD_LIBRARY_PATH would be fine.

> By the way, why not put "native" libraries to $prefix/share/kaffe?

`share' is expected to contain files that can be shared across
multiple architectures/OSs/whatever.  According to the GNU standards,
they should be in the `lib' directory, but `lib/kaffe' would not be a
bad idea.

-- 
Alexandre Oliva
mailto:oliva at dcc.unicamp.br mailto:aoliva at acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil