History

Basile Burg 1a4240fe9e use same naming convention for version.txt and git tags		2016-07-09 21:35:00 +02: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	use same naming convention for version.txt and git tags	2016-07-09 21:35:00 +02:00
cesetup.d	use same naming convention for version.txt and git tags	2016-07-09 21:35:00 +02:00
cp-rpm-files-nux64.sh	cesetup, updated for dastworx	2016-07-02 17:10:42 +02:00
readme.md	cetodo, use a static array and not an aa	2016-02-22 07:18:57 +01: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	use same naming convention for version.txt and git tags	2016-07-09 21:35:00 +02:00
zip-nux32.sh	use same naming convention for version.txt and git tags	2016-07-09 21:35:00 +02:00
zip-nux64.sh	use same naming convention for version.txt and git tags	2016-07-09 21:35:00 +02:00
zip-win32.bat	cesetup, updated for dastworx	2016-07-02 17:10:42 +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 3 configurations named win32, nux32, _nux64. Each takes the content of the matching sub-folder and puts 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 text in the version.txt file.
change the setup program outputFilename for each configuration, according to the new version.
put the content (programs, icon, license, etc.) in each of the nux32/nux64/win32 folders.
compile on each platform with the right project configuration.