On Fri, Aug 15, 2008 at 12:21:28PM +0200, Markus Schönhaber wrote:
> Jens Seidel wrote:
> Eclipse, like any other Linux process, probably doesn't care about
> LD_LIBRARY_PATH. But that's beside the point. It's the dynamic linker
> that cares about it.
Yep, of course.
> To have any effect, it should be obvious that LD_LIBRARY_PATH has to be
> propagated to the corresponding process's (Eclipse's) environment. So,
> depending on how you start Eclipse you may have, for example, to
> "export" LD_LIBRARY_PATH.
I remember that on a 64 bit platform javahl was not found by default by
Subclipse in /usr/lib64/ which is one of the default linker paths on
this system (there was an entry in /etc/ld.so.conf). As far as I
remember it was explained on this list that java behaves differently
and doesn't follow ld's configuration.
You might be right that LD_LIBRARY_PATH is respected by Eclipse but in
general it's useless to put /usr/lib64 into it as ld already knows about
it :-)
> > You have to start Eclipse with the option
> > -Djava.library.path=/usr/lib64 (which should point to the location of
> > the lib) after the option -vmargs.
>
> That's an alternative approach. But not the only way to do it.
> The drawback of explicitly setting java.library.path is that it's value
> will be overridden while the value of LD_LIBRARY_PATH will be added to
> the value of java.library.path. Depending on one's needs this may or may
> not be something to care about.
Thanks for this information. Your LD_LIBRARY_PATH solution has at least
the advantage that I can easily remember it which isn't true for
-Djava.library.path ...
Jens
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-15 12:51:59 CEST