dexed/setup
Basile Burg 22f0a5cf39 rlz 2023-09-18 08:41:22 +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
Dockerfile change the image used to build the releases 2023-07-07 01:49:50 +02:00
build-release.sh patch use of deprecated API property 2023-08-24 12:12:45 +02:00
build-rlz-image.sh change the image used to build the releases 2023-07-07 01:49:50 +02:00
deb.sh simplify the deb package dependency list , close #72 2020-11-23 02:45:17 +01:00
delete-gitlab-artifacts.sh fix changelog typos 2020-04-17 14:32:10 +02:00
extract_last_changelog_part.d fix #23 - regex to take last changelog part does not work 2020-04-09 11:14:50 +02:00
readme.md rlz 2021-09-25 16:52:28 +02:00
rpm.sh rpm, prevent dependency on specific on gitlab runner used to release 2020-04-28 21:47:24 +02:00
setup.d build windows releases using appveyor and move source for lazarus binaries to a gitlab repo 2020-08-31 02:27:03 +02:00
setup.dprj rlz 2021-10-11 08:01:41 +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 rlz 2023-09-18 08:41:22 +02:00
zip-nux32.sh fix linux zip files 2020-04-17 13:46:23 +02:00
zip-nux64.sh fix linux zip files 2020-04-17 13:46:23 +02:00
zip-win32.bat remove unfortunate JSON property leading to double "lib" prefix and add temp changelog 2020-04-17 14:07:57 +02:00
zip-win64.bat remove unfortunate JSON property leading to double "lib" prefix and add temp changelog 2020-04-17 14:07:57 +02:00

readme.md

This folder contains the files necessary to manually build dexed and its toolchain or to build a dexed release

Requirements

Building

  • git
  • Freepascal ~> 3.2.0
  • Lazarus ~> 2.0.12
  • ldc2

Releasing

Same tools as to build plus:

  • rpm
  • dpkg
  • zip

Build manually dexed and the toolchain

  • in the project root directory bash setup/build-release.sh

Building a dexed release

  • prepare what will be the new tag, following semantic versioning rules
  • update the occurences of the tag in the main readme.
  • change the content of the version.txt accordingly.
  • commit the changes, for historic reasons the commit message should be "rlz"
  • add a git tag on the commit just created.
  • in the project root directory run bash setup/build-release.sh

The installers are produced in the output directory.