64 bit JRE when using JNI Headers
Brought to you by:
grzegok
Menu
▾
▴
Are there future plans to support a 64 bit JRE when using JNI headers?
Happy late 2020. I am curious to know the state of this as well. JNI headers are such a nice feature, having the users being able to see "MyProgram.exe" instead of "javaw.exe" in Task Manager and other places is awesome.
I think the main problem is that the exe-launcher created by Launch4j is a 32bit executable. A 32bit executable can not load a 64bit dll.
Therefore the launcher would have to be created as 64bit executable which makes it impossible to show an error dialog on a 32bit system.
The only way this could work would be if the 32bit launcher would also contain a 64bit executable which then could load the JRE as a library. A pretty complicated set-up.
I mean, what about all of the hundreds of other programs that ship both a 64-bit and a 32-bit executable? What's stopping Launch4j from doing that, creating both a 64-bit and a 32-bit version? I mean come on guys, it's 2020, Windows doesn't even support 32-bit systems anymore, and realistically nobody else does. In this day and age are we really still going to choose 32-bit over 64-bit?
Because Launch4j is at the moment designed to only build one version.
Of course you can extend the project, include all the build tools for building 64bit executables, extend the configuration GUI and the overall project to allow two different code paths and so on.
Launch4j is open source therefore you are invited to extend the project so that it works this way.