Profiles

Forums

Everything posted by liontiger

Hello Martin,
There is no documentation (besides built-in help) for most of our command-line tools. Most notable exceptions are jc and xpack, which are JET compiler and JET packager respectively.
The xlink tool is our linker and should not be used explicitly, thus it is not documented.
As for xxd -- I have no idea, what this tool could be.
Best Regards, Ivan

Hello Jane,
Currently Excelsior JET doesn't support cross-platform builds.
So in order to compile application for target Linux machine, you will need to use Excelsior JET for Linux, on a Linux building machine (either hardware or virtual machine can work).
Note however, that Excelsior JET doesn't support Unix targets except for OS X.
So if you are trying to compile for Unix (e.g. FreeBSD-based system), you can try compiling for Linux and running the application in Linux Binary Compatibility mode (see https://www.freebsd.org/doc/handbook/linuxemu.html).
We have not tested this approach, so it may or may not work for you or target Unix system.
Best Regards

JIT caching was deprecated in version 8.0 of Excelsior JET and has been removed since.
As for excessive JIT compilation:
Could you please try specifying all dependencies' jars as `!CLASSPATHENTRY` equations?
You can remove all `!module` equations as well as `-CLASSABSENCE=HANDLE` and `-IGNOREMEMBERABSENCE+` to see which dependencies are missing from compilation set.
Also, have you tried using our Maven or Gradle plugins and/or Jet Control Panel tool?
Best Regards,
Ivan Trepakov
Excelsior Support

These options are specific to Oracle HotSpot and its GC. Excelsior JET has its own Garbage Collector with its own set of options that cannot be mapped to or from HotSpot ones.
So you can remove all of the -XX options and see if your application works fine on our GC.
If after that your application will require any tuning you will have to do it using properties described in Excelsior JET User's Guide: https://www.excelsiorjet.com/docs/jet/jetw010#0321

Hello,
Can you elaborate which operating system you are using and from where and to where you are trying to copy-paste the line (e.g. from terminal to JET Control Panel "Command line:" text box while creating "Plain Java SE Application")?
Best Regards,
Ivan Trepakov

Just to reiterate what has been discussed with @AndyDenby over email and to provide a public statement on this issue:
It is highly discouraged to manually alter `java.class.path` property. If you will attempt to do it, you must provide ALL dependencies explicitly in that class path.
So for this particular case the suggested workaround is:
1. Remove altering of `java.class.path` from `jvmArgs` configuration. Gradle plugin will handle adding all dependencies into class path on its own.
2. Exclude packaged configs (which you want to change after deployment) from created .jar file using following configuration:
jar {
exclude('config')
}
Assuming that all packaged config files are located in 'config' directory inside of .jar.
The reason for such workaround is that Gradle plugin currently searches import class path entries before external class path entries, so if you don't exclude configs from .jar, JVM will find them in resources of compiled .jar file instead of your packaged external configs.
There is a ticket in Excelsior JET Gradle plugin's bug tracker to add proper support for modification of `java.class.path` - https://github.com/excelsior-oss/excelsior-jet-gradle-plugin/issues/36