Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #39529

Re: java.library path lib.*.so v *.dll

Show all headers | View raw

On 7/4/2020 1:20 PM, vjp2.at@at.BioStrategist.dot.dot.com wrote:
> It seems mind boggling that a "machine independent: java would use DLL.

     Java is machine-independent (in some sense of the phrase).  That
implies there are machine-specific things Java cannot do.  When an
application wants to do something machine-specific that is beyond Java's
power, it can write the machine-specific bits in another language (often
C++ or C), put those bits in a library, and tell the Java code how to
find and call them.  The whole Java-works-with-a-foreigner framework is
called the "Java Native Interface," or JNI.

     It seems the application you are struggling with is written in a
mixture of Java and something else, and that the "something else"
pieces reside in a library.

> What is .so?

     A "shared object," Unix' moral equivalent of a Windows DLL.

> Was it exclusive to RDKIT or is it a Java thing?

     Sorry; I have no idea.  Is the available documentation helpful?
Look for a "how to install" or "system prerequisites" section, or
something of that kind.

-- 
esosman@comcast-dot-net.invalid
Trump relies on his gut, that is, on his toxic waist.
Two hundred days to go.

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

java.library path lib.*.so v *.dll vjp2.at@at.BioStrategist.dot.dot.com - 2020-07-04 17:20 +0000
  Re: java.library path lib.*.so v *.dll Eric Sosman <esosman@comcast-dot-net.invalid> - 2020-07-04 14:16 -0400
    Re: java.library path lib.*.so v *.dll vjp2.at@at.BioStrategist.dot.dot.com - 2020-07-06 05:06 +0000

csiph-web