Re: JNI Installation Directories (again)
From: Ben Burton <benb@acm.org>
Subject: Re: JNI Installation Directories (again)
Date: Tue, 29 Oct 2002 07:03:28 +1100
> My argument for /usr/lib/jni is that other programs aren't going to want to
> link with them, so it's better not to clutter up the default shared library
> paths.
>
> It's the same reason C python modules are placed beneath /usr/lib/pythonX.Y -
> these are just libraries, but you only ever use them as python imports, so
> you avoid cluttering up /usr/lib.
I don't want to disturb your proposal but I want to say my humble
opinion.
Python case, there is one implementation and it's use /usr/lib/pyhon
default. So, it's not problem. But in Java case, there are a lot of
non-opensource implementation and they don't use /usr/lib/jni
default. So, users must set library path manually and some of them may
confuse about it.
But if put JNI libraries into /usr/lib, it's easy.
Takashi Okamoto
Reply to: