Greenstone Wiki

User Tools

Site Tools

You are here: index » en » developer » release_kits
en:developer:release_kits

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
en:developer:release_kits [2018/03/26 23:10] – [create-installer] kjdonen:developer:release_kits [2018/03/26 23:11] – [compile] kjdon
Line 97: Line 97:
 Each is explained in detail below. Each is explained in detail below.
  
-==compile==+  ***compile**
 This target compiles the native binary executables and the documentation for the release. It checks out the Greenstone3 source code from the repository into a folder called ''greenstone3''. It then compiles it by running ''ant'', automatically editing files, and so on. It basically simulates what an svn user would do to compile Greenstone3 but with a few small differences. One such difference is that it compiles everything statically. This target compiles the native binary executables and the documentation for the release. It checks out the Greenstone3 source code from the repository into a folder called ''greenstone3''. It then compiles it by running ''ant'', automatically editing files, and so on. It basically simulates what an svn user would do to compile Greenstone3 but with a few small differences. One such difference is that it compiles everything statically.
  
Line 107: Line 107:
 This target creates an executable jar installer for Greenstone3, and puts it in a directory called ''installer''. It uses the files in ''distribution/greenstone3''. It uses the ''ant-installer'' package included with the release kit. This target creates an executable jar installer for Greenstone3, and puts it in a directory called ''installer''. It uses the files in ''distribution/greenstone3''. It uses the ''ant-installer'' package included with the release kit.
  
-==wrap==+  ***wrap**
 This target wraps the executable jar installer in a native executable, and puts it in a directory called ''wrapped-installer''. It also creates another copy with a bundled JVM. This target wraps the executable jar installer in a native executable, and puts it in a directory called ''wrapped-installer''. It also creates another copy with a bundled JVM.
 ===sork2 and sork3=== ===sork2 and sork3===
en/developer/release_kits.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1