-
Notifications
You must be signed in to change notification settings - Fork 22
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
na-mainloop: Drop unneeded cargo-apk
setup and add xbuild
docs
#9
base: main
Are you sure you want to change the base?
Conversation
ac61f12
to
5e30ef6
Compare
Yeah this sounds probably ok if they can Just Work(tm) - maybe the gradle builds could be configured with the same application Id that cargo apk / xbuild will come up with by default. Does xbuild have the same default as cargo apk here? Btw, it would be kinda interesting to know if it would be possible to have xbuild also work with the agdk examples at some point, and those would need some kind of config for knowing to fetch the game-activity dependency. |
Afaik they're different. |
|
|
I don't really know where to start with configuring xbuild without looking at the implementation atm, the README doesn't show any examples and I haven't seen it reference any example projects. Can you maybe link to some open source example with an xbuild config to get a starting point for knowing what's configurable? |
Maybe @dvc94ch has a link. Afaik it's "as simple as" setting Supposedly it creates a bunch of files in the source dir for you, at least if https://github.com/rust-mobile/xbuild/tree/master/xbuild/src/gradle |
e5251b5
to
8d7cb4a
Compare
Without configuration `cargo-apk` uses the default `rust.<package>` namespace, instead of the hardcoded `com.foo.bar`. Similarly `xbuild` can build and run this project out of the box, no extra configuration (nor installation / dependencies!) required.
8d7cb4a
to
e95e9c4
Compare
Well this is awkward. The Ubuntu VM probably has a weird/old |
I just ran into this myself while trying to teach
Its precedence is not documented at https://doc.rust-lang.org/cargo/reference/config.html#buildrustflags, but it probably falls at position 3. (after |
Without configuration
cargo-apk
uses the defaultrust.<package>
namespace, instead of the hardcodedcom.foo.bar
. Similarlyxbuild
can build and run this project out of the box, no extra configuration (nor installation / dependencies!) required.Draft because it seems we have a lot more projects to clean up, and maybe even guides to deduplicate...