Better documentation of capability to store and extract native libraries

[GoogleCodeExporter]

Aside from the brief mention of self-extraction of DLL files in the FAQ, 
the capabilty of JNAerator to automatically store and extract DLL files is 
not well documented. Perhaps you could address the following in your 
documentation:
1. JNAerator bundles its own runtime library in the output jar file, 
including LibraryExtrator, which automatically extracts required native 
libraries.
2. The location where native library files are extracted to. (And what if 
I want to change this location)?
3. How to store and extract files that don't end in your default 
extensions (so|dll|dylib|jnilib), such as auxiliary files that my DLLs 
depend on.

This store-and-extract capability is not included in JNA, but I imagine 
many people find it useful. So perhaps you should more strongly promote 
this capability in JNAerator!

Original issue reported on code.google.com by Jonathan...@gmail.com on 24 Jan 2010 at 2:31

[GoogleCodeExporter]

Hi,

Thanks a lot for this suggestion. The doc is clearly a weak point of JNAerator 
right now...
I'm going to update the documentation a bit, as well as providing better 
support for arbitrary file extraction.

Stay tuned !

Cheers
--
Olivier

Original comment by olivier.chafik@gmail.com on 24 Jan 2010 at 10:49

• Changed state: Accepted

[GoogleCodeExporter]

Hi,
This issue moved to Github :
https://github.com/ochafik/nativelibs4java/issues/178

Thanks for not updating this page anymore and adding further comments on Github.
Cheers
--
zOlive

Original comment by olivier.chafik@gmail.com on 1 Sep 2011 at 7:28

• Changed state: MigratedToGitHub