Automating building installers

[Bastiaan Olij]

Hi Paul,







The VCS can already do automated builds - we setup scheduled builds using Studio 5 and Linux, and then had a cron job to copy the lib files to the appropriate place and compile our release.I'm aware of this but it requires Omnis to be running with GUI and all if I understand correctly. I want to run everything headless and a build process isn't hard to make. I will look into it again though, I haven't looked at Omnis' build in scheduled builds for years :)










We use the Inno Setup installer builder for windows, and Package Maker for Mac.  Inno Setup is pretty easy to use, and I'm sure it's scriptable.Same issue for me as Alex's reaction, this is no different for me then using bitrock other then maybe a better deliverable. I'm hoping for a solution that allows me to build installers without the need of a Windows or Mac OS machine so I can just run it as part of my docker scripts that build the images that I deploy to our servers.


However, little do I know, just reading through the help pages of bitrock, since I last looked into this a few years back when we first started code signing, they added cross platform code signing so I can run it on Linux and build fully signed Mac OS X and Windows installers. Learned something new today.


(still a bit of a sore point because I want to switch to msi and pkg).











I found a link on Stack Overflow to code signing windows software on linux, using the mono framework - https://stackoverflow.com/questions/18287960/signing-windows-application-on-linux-based-distros
Sweet! thanks! If I do stray away from bitrock (MSI is really the important one for use to support) this is invaluable info :)


Cheers,


Bas