setup program, zip output using post build process

cesetup/cesetup.coedit

@@ -17,6 +17,10 @@ object CurrentProject: TCENativeProject
         '/c'
         ' zip-win32.bat'
       )
+      postBuildProcess.executable = 'zipsetup-win32.bat'
+      postBuildProcess.parameters.Strings = (
+        '<CPO>'
+      )
     end  
     item
       name = 'nux32'
@@ -33,6 +37,11 @@ object CurrentProject: TCENativeProject
       preBuildProcess.parameters.Strings = (
         'zip-nux32.sh'
       )
+      postBuildProcess.executable = 'sh'
+      postBuildProcess.parameters.Strings = (
+        'setupzip-nux-noarch.sh'
+        '<CPO>'
+      )
     end  
     item
       name = 'nux64'
@@ -49,6 +58,23 @@ object CurrentProject: TCENativeProject
       preBuildProcess.parameters.Strings = (
         'zip-nux64.sh'
       )
+      postBuildProcess.executable = 'sh'
+      postBuildProcess.parameters.Strings = (
+        'setupzip-nux-noarch.sh'
+        '<CPO>'
+      )
+    end  
+    item
+      name = 'devel-win32'
+      messagesOptions.tlsInformations = True
+      outputOptions.inlining = True
+      outputOptions.boundsCheck = offAlways
+      outputOptions.optimizations = True
+      outputOptions.release = True
+      pathsOptions.outputFilename = 'output\coedit.1update2.win32.setup.exe'
+      pathsOptions.importStringPaths.Strings = (
+        'win32\'
+      )
     end>
   Sources.Strings = (
     'cesetup.d'

cesetup/readme.md

@@ -1,22 +1,26 @@
+This folder contains the files necessary to make a Coedit release.
+The process is semi-automated and achieved by compiling a project in Coedit itself.
+
 Coedit setup program
 ===
 
-This coedit project creates the coedit setup program.
-The project contains 3 configurations. Each one takes the content of one of the nux32/nux64/win32 folders
-and put it in the output program at compile time (eg .data section). 
+This coedit project (_cesetup.coedit_) creates the coedit setup program.
+The project contains 4 configurations:
+
+- _devel-win32_: it does not takes part in the release process. 
+- win32, nux32, nux64: they take respectively the content of their matching sub-folder and put it in the output program at compile time (using the `import(file)` expression).
+The output program is then compressed by the post-build process, using the scripts named `setupzip-<arch>`.
 
 Raw Zip
 ===
 
-The shell scripts take the content of the nux32/nux64/win32 folders to make some simple zip files.
-They are proposed alternatively to the setup program. The scripts are launched automatically when
-the setup program is about to be compiled (as pre-build process).
+The shell scripts named `zip-<arch>` take the content of their matching sub-folder to make an archive.
+They are proposed alternatively to the setup program. The scripts are launched automatically when the setup program is about to be compiled (as pre-build process).
 
 Todo by hand for each release
 ===
 
 - change the setup program _outputFilename_ for each configuration as well as the text printed to the console, according to the new version.
 - change the text in the _version.txt_ file.
-- put the content (programs, icon, license, etc.) in each of nux32/nux64/win32 folders.
-- compile on each platform with the right project configuration.
-- zip the setup programs. (in the future: as a post-build process ?).
+- put the content (programs, icon, license, etc.) in each of the nux32/nux64/win32 folders.
+- compile on each platform with the right project configuration.

cesetup/setupzip-nux-noarch.sh

@@ -0,0 +1,4 @@
+cd output
+zip -9 -j $1.zip $1
+rm -f $1
+rm -f $1.o

cesetup/setupzip-win32.bat

@@ -0,0 +1,4 @@
+cd output
+7z a -tzip -mx9 %~n1.zip %1
+if exist %1 del %1
+if exist %~n1.obj del %~n1.obj