-
Notifications
You must be signed in to change notification settings - Fork 63
Update GameActivity from v2.0.2 to v4.0.0 #188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I do wonder if it'd be easier to keep a fork of |
would definitely make rebasing easier because it was kind of a PITA to fix all the paths on the patches |
There should be an arg to automate stripping the paths, but yeah it's extra confusing (especially the commit history here!) to first revert all the patches, then copy the new code, and finally reapply. I would hate to have to redo that for every release, instead we can just have rebased branches+tags for every upstream release in a fork. |
downside is that a depth1 clone of gamesdk is like 175MB |
If we do want to eventually do this I pushed v4.0.0 with our patches here: https://github.com/jb55/android-games-sdk-rs/tree/android-activity-4.0.0 |
I also squashes a few of the the patches and made them more logically separated: jb55/android-games-sdk-rs@v4.0.0...android-activity-4.0.0 the maybe |
Although I'm initially sceptical of using A workflow where we rebase patches on an upstream branch and then just import a snapshot of the game-activity source that we need (with clear references to the branch we've imported from) could be practical enough without needing to introduce a dependency on submodules. Maybe we can stream line that a little with some |
Uh oh!
There was an error while loading. Please reload this page.
As per some discussions here:
It seems like there are upstream GameTextInput fixes since v2.0.2, so we should try to update our local version. The plan is to re-apply our local patches on top of v4.0.0.
It's a bit of a pain to keep these in sync, there have been discussions around creating a RustActivity so we don't have to keep resyncing with GameActivity, but I'll leave that for another issue.
Patches to apply
Last import on repo:
Patch plan
The plan is to save these as patches and then apply them on top:
One challenge is that there have been some formatting commits upstream:
So I may need to format our patches first? bleh.
Changes in
v2.0.2..v4.0.0
One update:
update default_motion_filter()
is the same fix I PR'd here:
The text was updated successfully, but these errors were encountered: