Self-extracting jre instructions
_________________________________

1. You need 7za.exe and 7zCon.sfx from the shared/windows/7za folder folder to generate the self-extracting jre from a jre. 


2. Need the jre for your java version.

Now we grab Azul Zulu JREs, which use OpenJDK, from https://www.azul.com/downloads/?version=java-11-lts&os=windows&package=jre#zulu

We now generate 64 bit and 32 bit windows binaries, so we need to do this process for 64 bit and 32 bit architecture.

Download the appropriate zip file, then unpack it. You'll end up with a top-level folder called something like zulu11.82.19-ca-jre11.0.28-win_x64. This will contain bin, lib folders and a release file (among other things). Makesure you haven't got double zulu... folders. Rename this zulu folder to 'jre'.

- When the Greenstone installer runs, the jre will end up extracted into a folder named jre.
- Don't tar the jre for Windows Greenstone. (But Greenstone linux/mac expects the jre to be tarred up first.)

3. From the gs-release-builder/release-kits/shared/windows folder, Run:

     7za\7za.exe a -sfx -mx=9 jre.exe C:\Path\to\jre

This will generate the jre.exe. Move it into the wrapper folder. The 32 bit version should be called jre.exe, and the 64 bit version should be renmaed to jre_x64.exe

* -m0=lzma2 is already done automatically, setting the compression mode to lzma2.
* -mx=9 set its (compression? speed?) to ultra
* the output file name expected by the release-kit is jre_bin for 32 bit linux, jre_bin_x64 for 64 bit linux
* -sfx indicates that it will generate a self-extracting binary out of the input file
* the "a" indicates it will add the files from the input folder (the /path/to/your-jdk-version/jre in this case) to the output file


4. Test the jre.exe produced: double click. For Greenstone on Windows it should produce a jre folder.
If all went well, commit the jre.exe and jre_x64.exe (in the wrapper folder). Note, if you are upgrading the version of java, rename the existing ones with their current version number and commit.


5. Run the nightly release kit, then test the generated release binary by running the installer on a different Windows machine to the one that generated the release.