puzzles/winwix.mc, branch rockbox My sgt-puzzles tree Reinstate 32-bit Windows builds of Puzzles. 2017-11-26T21:11:35+00:00 Simon Tatham anakin@pobox.com 2017-11-26T20:12:15+00:00 3cf09c261591b939df53c5357ab471c5b3076d22 I've built a set of 32-bit binaries, a 32-bit zip file and a 32-bit MSI, all delivered into a 'w32' output directory. 
I've built a set of 32-bit binaries, a 32-bit zip file and a 32-bit
MSI, all delivered into a 'w32' output directory.
Switch the Windows builds over to clang-cl. 2017-08-24T19:07:20+00:00 Simon Tatham anakin@pobox.com 2017-08-24T18:12:54+00:00 9d89550a75393723c5937559fa86a434de4a77f0 This also switches them to being 64-bit, which I think is probably acceptable in this modern age, especially for such a non-essential piece of software. If anyone complains I can always reinstate a parallel 32-bit build. To support the switch to 64-bit, this commit also changes the default install directory in the MSI to 'Program Files' rather than 'Program Files (x86)'. 
This also switches them to being 64-bit, which I think is
probably acceptable in this modern age, especially for such
a non-essential piece of software. If anyone complains I can
always reinstate a parallel 32-bit build.

To support the switch to 64-bit, this commit also changes the default
install directory in the MSI to 'Program Files' rather than 'Program
Files (x86)'.
Use WiX to generate an MSI-based Puzzles installer. 2016-03-10T18:37:24+00:00 Simon Tatham anakin@pobox.com 2016-03-10T18:37:24+00:00 fc6cc8fb2b9cbc97ccd6a74c8953cc1920013141 I've reused most of the install script I wrote for PuTTY recently, minus the selectable-features dialog, and plus some preliminary Mason templating to automatically build the right set of puzzle binaries into the installer. Stable GUIDs are autogenerated by the same technique I use in PuTTY's Visual Studio project file generation: hash a fixed pile of randomly generated bits (that is, randomly generated _once_ and used forever) with each filename or other identifier and use those as your random number source. 
I've reused most of the install script I wrote for PuTTY recently,
minus the selectable-features dialog, and plus some preliminary Mason
templating to automatically build the right set of puzzle binaries
into the installer.

Stable GUIDs are autogenerated by the same technique I use in PuTTY's
Visual Studio project file generation: hash a fixed pile of randomly
generated bits (that is, randomly generated _once_ and used forever)
with each filename or other identifier and use those as your random
number source.