dexed/cesetup
Basile Burg d718f35304 not an option 2015-12-21 00:31:01 +01:00
..
nux32 added cestup, the coedit setup program 2015-06-04 03:37:42 +02:00
nux64 added cestup, the coedit setup program 2015-06-04 03:37:42 +02:00
win32 added cestup, the coedit setup program 2015-06-04 03:37:42 +02:00
.gitignore setup program - zip are launched as pre-build process 2015-08-25 20:42:47 +02:00
cesetup.coedit updated version num 2015-12-20 15:14:46 +01:00
cesetup.d not an option 2015-12-21 00:31:01 +01:00
readme.md update 2015-08-28 01:12:28 +02:00
setupzip-nux-noarch.sh setup, refact using array of Resource, + fix zip script + update ver 2015-12-05 08:10:19 +01:00
setupzip-win32.bat setup program, zip output using post build process 2015-08-27 00:15:11 +02:00
version.txt updated version num 2015-12-20 15:14:46 +01:00
zip-nux32.sh fix version file not expanded insh scripts 2015-08-25 21:28:48 +02:00
zip-nux64.sh fix version file not expanded insh scripts 2015-08-25 21:28:48 +02:00
zip-win32.bat updated script that make the zips 2015-08-25 20:34:13 +02:00

readme.md

This folder contains the files necessary to make a Coedit release. The process is semi-automatic and achieved by compiling a project in Coedit itself.

Coedit setup program

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 the content of their matching sub-folder and put it in the output folder, as an extractor program, at compile time (using the import(file) expression). The extractor program is then compressed by the post-build process, using the scripts named setupzip-<os & arch>.

Raw Zip

The shell scripts named zip-<os & 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 the nux32/nux64/win32 folders.
  • compile on each platform with the right project configuration.