jonpas
Similar or almost the same as #41, @bux move discussion there?
I don't think we'll provide full setup for exactly what you want, but just splitting sign step out so you can write your own scripts inside HEMTT configuration for it....
Not just PBOs, for file patching to work with optionals we'll want to move the entire addon folder over. Still not sure how to best do that to be easy...
It's just not implemented in armake2 itself yet.
Flag is there, so I assume so.
https://github.com/KoffeinFlummi/armake2/pull/16 API would of course be very nice so we don't have to replicate armake2's code.
Looks like `GIT_HASH` environment variable just isn't set for Windows compilation, ref.: https://github.com/synixebrett/HEMTT/blob/master/src/lib.rs#L40
That one was a CI build. CI doesn't read the hash as per my last comment.
Can reproduce the same way, not the original bug with 0.7.5. Maybe it was fixed in CI at some point (addition of GitHub Actions?), but this was introduced.
There is already self-update `hemtt update`. Just no self-checking etc. I don't think that's very important with project-specific versions as it works now, as each project will add the version...