dexed/setup
Basile Burg a9af7323eb update version 2019-06-10 21:21:16 +02:00
..
.gitignore update version and add config to build full 64 bit win rlz, close #367 2019-01-02 23:10:40 +01:00
deb.sh rename as Dexed, "D extended editor" 2018-10-20 13:28:15 +02:00
readme.md fix more old names 2018-10-21 15:31:16 +02:00
rpm.sh update links 2019-01-19 17:40:54 +01:00
setup.d fix #473 - sudo setup and ownership of the folder containing the settings 2019-05-16 00:56:09 +02:00
setup.dprj update version 2019-06-10 21:21:16 +02:00
setupzip-nux-noarch.sh update version 2018-10-21 14:54:17 +02:00
setupzip-win-noarch.bat update version and add config to build full 64 bit win rlz, close #367 2019-01-02 23:10:40 +01:00
version.txt update version 2019-06-10 21:21:16 +02:00
zip-nux32.sh rename as Dexed, "D extended editor" 2018-10-20 13:28:15 +02:00
zip-nux64.sh rename as Dexed, "D extended editor" 2018-10-20 13:28:15 +02:00
zip-win32.bat fix win scripts that zip the binaries 2019-04-04 19:55:04 +02:00
zip-win64.bat fix win scripts that zip the binaries 2019-04-04 19:55:04 +02:00

readme.md

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

dexed setup program

The dexed project (cesetup.dxp) creates the dexed setup program. It 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 extraction program, at compile time (using the import(file) expression).

The extraction 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 version field.
  • put the content (programs, icon, license, etc.) in each of the nux32/nux64/win32 folders.
  • compile on each platform with the right project configuration.
  • run the rpm.sh and the deb.sh scripts.