Hello and welcome!I'm thinking that I may set this up for a new release 1.32 - or can throw this back to hoglet67 once I've cleaned it up and its been tested a bit. I assume they're on the forum and may see this, so hi
This looks very interesting. Windows builds of Atomulator have always been a mess and this goes a very long way towards cleaning that up.
If I am understanding your approach here, the build is using github actions, so runs automatically in Microsoft's cloud. The build generates both Windows and Linux artifacts.
The Windows build uses a standard Windows Server 2025 image pre-loaded with lots of development tools including cmake, g++ and gcc. You are including allegro4, freealut and openal-soft as git submodules, and building these from source (with caching between builds). So the end result is a statically linked executable with no shared library dependencies. That's nice.
What versions of Windows would you expect this to run on?
The Linux build uses a standard Ubuntu 24.04.3 image also pre-loaded with lots of development tools. The build is pretty much unchanged from before, so allegro4, freealut and openal-soft are linked dynamically, as is libc. So this build is still going to be somewhat platform specific.
I wonder if the same build approach (creating a fully statically linked executable) could be used on the Linux builds as well?
I don't use Windows much myself now, but it would be great if folk with Windows could try to test the latest Windows build here
One minor thing that's slightly confusing here is the top level build is called "Windows Build", even though it generates artifacts for both Windows and Linux. I'm not sure where this name originated from. Could it be changed to "Atomulator Build"?
Oh, and feel free to bump the version to 1.32 when you are ready.
Dave
Statistics: Posted by hoglet — Thu Dec 04, 2025 9:29 am