Reply To: MWEdit
We have a downloadable build! If it runs, I can go ahead and get it added to the Releases page manually as you need to be logged in to GitHub to download build artifacts. Even with the limitation, it’s huge progress! I’ll also need to make an official announcement on the various sites since it’s the first build that’s been available in twenty years 🙂
It looks a bit small so there’s a chance the assets aren’t being packaged up as defined in the RC files. We may need to tweak the packaging script in the YAML file. Or simply distribute the assets alongside. Not entirely sure how to go about it but let’s see if the executable works first 🙂
I also found the list of actions that GitHub supports: https://github.com/actions
Looks like my dream of automated releases is dead: the two actions for releases are listed as unmaintained so that won’t do. We may just need to package things up manually periodically. A bit annoying but we’ll manage 🙂
Right now, the build artifact is a dynamic build so you’ll need to make sure the DevIL DLLs are alongside the executable when you run it. When I package it up for release, I’ll probably simply copy them over to the archive. Not a good long-term solution so we’ll need a better one. We could take a simply sledgehammer to it and make it static, which I’ve done in the past, or we could set it up as semi-dynamic. GCC supports two options, as an example: -static, which is a full static build with everything linked together in one executable, and -static-libstdc++, which is partially dynamic and only statically links the C++ library to it. Not sure of the various options in VS.
I’m also not sure if we can copy over the DLLs in the YAML file. It’d be nice to fully automate things, though. Will do some more reading at some point.
That being said, I don’t really know what the best way of handling the release packaging long-term would be. The options I’ve listed aren’t exactly all that elegant.
Edit:
Looks like something removed the BOM from the few files that had it automatically while I was doing repo work yesterday. Will need to take a closer look but I didn’t see it in any of the files today.