0.4 release?

[enumag]

Hi, I'm interested in using this library. It seems to be overall better than the other libraries I have been using so far.

It seems there have been quite a few improvements since the 0.3 release such as adding SRAL_GetEngineName, android support and other things. So I'd like to ask what's left to be done before 0.4 can be released?

I also noticed that the 0.3 zip doesn't contain the libSRAL.so and libSRAL.dylib files for ubuntu and macos. Is there some reason for that? Could they be included for 0.4?

[m1maker]

@enumag

Yes, unfortunately, there are problems with the releases. We don't have a workflow set up for automating this, and I don't have the ability to manually build the library for all supported platforms and architectures at the moment.

Additionally, I am not currently working on this project, but I will take your feedback into consideration and try to find a solution.

It is possible that one of the existing contributors can help me with this, and I will review and accept their contributions.

[enumag]

Entirely valid. It would indeed be best if the build process was automated for all platforms. (Personally I'd argue their support should not have been merged without it.)

Thanks for replying. 🙂

[JRJurman]

@enumag - you can look at builds on the latest branch, and that should have all the artifacts built for different platforms that would need it (note, in iOS or Android builds, you'll want to include the source anyways I believe) - https://github.com/m1maker/SRAL/actions?query=branch%3Amain

Candidly, I've never totally felt like the need for GitHub releases for small libraries like this was ever worth the effort, so I think, as long as that works for most folks, that should be sufficient.

[enumag]

It isn't sufficient because artifacts expire eventually. Also I prefer to use the latest stable version rather than the latest commit for stability reasons. There are no artifacts for 0.3 anymore.

[JRJurman]

Ah, I had not realized that artifacts expired! Well, we should be able to use the GitHub actions to publish the CI artifacts for a release. I'm not super familiar with how that is traditionally set up, but I'm happy to look into that (probably after I get my other PR in a good state 😅), or defer to other contributor's wisdom here.

[enumag]

It's not too complicated... You download the artifacts, copy the files you want from each artifact and make a release.
Here is an example: https://github.com/enumag/mkxp-z/blob/60ed0638c2b98f86faa64df2168585ac72e314d2/.github/workflows/autobuild.yml#L614-L691

The main reason why I'm not offering to do it myself is that I'm not familiar enough with this project to say which files should be in the release. 😅

[JRJurman]

I put a PR together for this in #38 - I realize there could be an artifact build for android and iOS, but still need to test that. Once that PR is approved and merged, I can start working on the android and ios versions.