anki: update to 25.07.3. adopt

[mmdbalkhi]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture, x86_64(glibc)

[ii8]

Would it make sense to use XBPS_TARGET_WORDSIZE instead? Otherwise if anki explicitly only supports 64 bit maybe it should be set in archs instead

[mmdbalkhi]

It's the runner that requires a 64-bit, not Anki itself. I'm not sure if it's possible to build runner on a 64-bit host machine and then use it to cross-build Anki for 32-bit targets without packaging the runner.

[historical-theology]

@mmdbalkhi , could you do another force push and update so that we can try to get this accepted by one of the hard working Void core team members? I am sure that I am not the only person who would appreciate having Anki available as a native package in Void rather than needing to use the Anki project's official (new) scripted setup. Thank you for doing this for all of our benefit.

[sburris0]

Is there anything I can help with to get this finished?

[ii8]

@sburris0 This PR doesn't build at the moment, that needs to be fixed. The logs have expired so no clue what the problem was, you'll have to try building to find out.

[mmdbalkhi]

Sorry for late reply @sburris0 @ii8
cross-build fails because anki's build runs target-arch helpers (configure/runner) on host, but they need qemu to run (no native exec)

For example, see this:

https://github.com/ankitects/anki/blob/5614d20bedcc4dd268136d389ad796b404a69d2c/build/runner/src/build.rs#L155-L158

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.