Currently developers need to use -Djava.library.path property to pass the native library path to VM.
Since it is a Java Property, it has it's own limitations. (Properties can't be repeated)
e.g. All of the native library paths has to be passed in on go with **platform specific path separator**.
(windows) -Djava.library.path=path/to/foo;path/to/bar;...;
(*nix) -Djava.library.path=path/to/foo:path/to/bar:
However if there is a proper JVM switch (as we have -class-path, -module-path), developer can easily use without any much ordering issues.
e.g.
--native-library-path path/to/foo --native-library-path path/to/bar
Since it is a Java Property, it has it's own limitations. (Properties can't be repeated)
e.g. All of the native library paths has to be passed in on go with **platform specific path separator**.
(windows) -Djava.library.path=path/to/foo;path/to/bar;...;
(*nix) -Djava.library.path=path/to/foo:path/to/bar:
However if there is a proper JVM switch (as we have -class-path, -module-path), developer can easily use without any much ordering issues.
e.g.
--native-library-path path/to/foo --native-library-path path/to/bar