The current runtime is hardcoded to the prebuilt build-2022-10-03-c5c7b07 release in my https://github.com/AppImage/type2-runtime fork:
|
urls = ["https://github.com/lalten/type2-runtime/releases/download/build-2022-10-03-c5c7b07/runtime-{}".format(runtime_arch)], |
There have not been any developments on the runtime since then, but it would be nice to build this from source instead of depending on someone's magic precompiled blob.
I do have a branch with a Bazel build for the runtime at lalten/type2-runtime#9.
The resulting binary is actually quite a bit smaller (likely due to being able to strip unused symbols and better compiler optimization for host/exec config tools), but I have not benchmarked its performance.
Upstream maintainers are not open to changing their rather complex build setup, so landing this is not an option.
The build uses Bzlmod and I have no desire to port everything to WORKSPACE.
So as long as rules_appimage supports WORKSPACE we can't (fully) switch to that yet.
The current runtime is hardcoded to the prebuilt
build-2022-10-03-c5c7b07release in my https://github.com/AppImage/type2-runtime fork:rules_appimage/deps.bzl
Line 28 in bcd4c72
There have not been any developments on the runtime since then, but it would be nice to build this from source instead of depending on someone's magic precompiled blob.
I do have a branch with a Bazel build for the runtime at lalten/type2-runtime#9.
The resulting binary is actually quite a bit smaller (likely due to being able to strip unused symbols and better compiler optimization for host/exec config tools), but I have not benchmarked its performance.
Upstream maintainers are not open to changing their rather complex build setup, so landing this is not an option.
The build uses Bzlmod and I have no desire to port everything to WORKSPACE.
So as long as rules_appimage supports WORKSPACE we can't (fully) switch to that yet.