I think I can use cross-compilation to build it, so I will temporarily convert it into a draft and open it after I finish.

@tonsky

Completed, ready for review.

Thanks!

@tonsky

It seems that 82cfc18 has damaged CI. Can you fix it?

After it is fixed, I can try to update and test the GitHub Action configuration of Skija.

I think it’s going fine so far. It just aborted already existing versions (by design) and only builds arm for linux

I think it’s going fine so far. It just aborted already existing versions (by design) and only builds arm for linux

Well, I may have misunderstood the meaning of the failed state in GitHub Action.

Because I don’t rebuild Skia too often, I also tend to forget about it and get scared. Luckily, when I click to see what’s going on, I see that check-release fails and that means this version was already compiled. I wish there was an alternative way to gently cancel the task (is there?)

Because I don’t rebuild Skia too often, I also tend to forget about it and get scared. Luckily, when I click to see what’s going on, I see that check-release fails and that means this version was already compiled. I wish there was an alternative way to gently cancel the task (is there?)

Maybe you can write environment variables through check_release.py and check environment variables in all subsequent operations? I don't know if there is a simpler way.