Updated README.

This commit is contained in:
LoRd_MuldeR 2020-10-01 22:40:18 +02:00
parent 1c51c4c4ca
commit ce03d84430
2 changed files with 10 additions and 4 deletions

View File

@ -160,6 +160,12 @@ public class YourMainClass {
}
```
## The JAR file name
Be aware that the same problem of “mangled” Unicode characters applies when the path of the JAR file is passed to the Java executable. In other words, the Java runtime *fails* to execute any JAR files whose path – file name or directory name anywhere in the path – contains any Unicode characters that cannot be represented in the computer's *local* ANSI codepage! Unfortunately, we can **not** encode the path of the JAR file as we do with the other command-line arguments, because the Jave executable requires the path of the JAR file to be passed in a non-encoded form.
Therefore, it is recommended to ***only*** use ASCII characters in the name of your JAR file and in the “install” path !!!
# Build instructions
In order to build Launch5j from the sources, it is recommended to use the [*GNU C Compiler* (GCC)](https://gcc.gnu.org/) for Windows, as provided by the [*Mingw-w64*](http://mingw-w64.org/) project. Other C compilers may work, but are **not** officially supported.

View File

@ -49,8 +49,8 @@ END
/////////////////////////////////////////////////////////////////////////////
VS_VERSION_INFO VERSIONINFO
FILEVERSION 0,5,0,0
PRODUCTVERSION 0,5,0,0
FILEVERSION 0,5,1,0
PRODUCTVERSION 0,5,1,0
FILEFLAGSMASK 0x17L
#ifdef _DEBUG
FILEFLAGS 0x3L
@ -67,8 +67,8 @@ BEGIN
BEGIN
VALUE "ProductName", "Launch5j"
VALUE "FileDescription", "Launch5j"
VALUE "ProductVersion", "0.5.0"
VALUE "FileVersion", "0.5.0"
VALUE "ProductVersion", "0.5.1"
VALUE "FileVersion", "0.5.1"
VALUE "InternalName", "Launch5j"
VALUE "OriginalFilename", "launch5j.exe"
VALUE "LegalCopyright", "Created by LoRd_MuldeR <MuldeR2@GMX.de>"