Several listeners or panels might need access to OS-dependent shared libraries. They are divided into
- built-in libraries,
- 3rd party libraries.
Built-in libraries are available for inclusion at compile time out of the box.
To minimize the size of resulting installers, each native library must be explicitly included. This is done by the
<natives> element can embed an unlimited number of nested
To add the same library for different processor architectures they must get a different name for each architecture and be added all.
Specifies the type of the native library:
|Any resource file name.||yes|
The file name of the resource to be added.
There must be a file name for each processor architecture, 32 and 64 bit. The 64 bit libraries must have the suffix
Any valid resource path.
Root path of the native resource. This is used for finding the resource to add. The destination path is always
In case src is set to a value the source path to get the native library from is assembled from the attribute values described here like this:
Native resources are needed for a couple of IzPack components. Built-in native libraries are:
The above libraries don't need this attribute to be set, the default path is the correct one here.
Using of the src attribute makes sense if you add your own libraries in an additional jar file using the
This attribute is ambiguous and marked deprecated beginning from 5.0.7 (compiler warning). Use the
The value "
By default, the native library is available just during the installation, but not in the uninstaller.
For using the Shortcut Panel on Windows there are required the ShellLink native libraries to access some native APIs:
Both 32-bit and 64-bit versions are built-in to IzPack.