Determine which executable files to build

The Archive Builder and the Native Executable Builder are features of JBuilder SE and Enterprise.

This step of the Archive Builder and the Native Executable Builder determines which native executable files are generated. The application's JAR file is automatically bundled with native executable wrappers for easy deployment to various platforms.

Note: The JDK is not bundled with the JAR file. The JDK must be installed on the user's computer in order for the executable to run.

Important: You must specify a main class on the previous step or the executable won't run.

Create the selected native executables

Select any or all of the native executables listed. By default, JBuilder generates the selected executables and saves them with the project name and the appropriate file extension at the root of the current project directory. Choose the ellipsis button next to the selection to change the default executable name and/or save it to a different location. Choose from any of these native executables:

Running executables

Note that the JDK is not bundled with the JAR file, so the JDK must be installed on the user's computer in order for the executable to run. The platform-specific executable file looks for the installed JDK in the following location:

If you create the executable on the Windows platform and move it to other platforms, you may need to change the permissions to make it executable.

Choosing the Mac OS X option creates an application that is launchable only from a command line. In order to create an application that is launchable from the Finder, Mac users need to create an Application bundle. Please refer to Apple's Mac OS X Developer documentation with regards to bundles and application packaging.