Migration to Delphi XE5
Migration now had three main tasks for me:
1. update project package files
2. fix a few compiler errors
3. rewrite the whole build process on heidisql.com
The build process was previously based on a mixture of batch files in the "extra" directory of the HeidiSQL sources and a PHP script writing binaries into a MariaDB database from where downloads are served. I decided to remove the batch files as these used the quite uncommon syntax of extended DOS shell commands, including for-loops, variables and parameter parsing.
So now I have a pure 200-liner of a PHP script which:
* does a Subversion update
* calls the Delphi command line compiler
* pulls and compiles translation files from Transifex, using tx.exe and msgfmt.exe
* patches the compiled executable with the madExcept handler using madExceptPatch.exe
* creates the installer with InnoSetup, using ISCC.exe
* and finally writes the executable, the installer and a build log to the database which serves downloads.
All went well, I now have a more maintainable build process, and the first heidisql.exe has just been built (r4592). You will probably notice the increased size of the nightly builds, which are roughly 1.2M bigger than previously. Well, nothing to worry about.
Earlier versions of HeidiSQL were compressed with UPX, a nice .exe compressor. But as I began to use the madExcept handler, it could no longer find the right callstack details, so I had to remove that compression.
Anyone out there preferring a 64bit version of HeidiSQL over the 32bit version?
To sum up: are there any drawbacks, apart from the obvious ones (i.e., compiling everything twice)?
Please login to leave a reply, or register at first.