Skip to content
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

Issues with name x and xbuild #154

Open
fredrik-hammar opened this issue Nov 29, 2023 · 3 comments
Open

Issues with name x and xbuild #154

fredrik-hammar opened this issue Nov 29, 2023 · 3 comments

Comments

@fredrik-hammar
Copy link

First, I would just like to say that this project seems really cool! I'm planning on using it myself and already made a demo for using it on android with egu, egui-android-demo :-)

But I think you'll have some problems with the current name.

The name xbuild is used by several other tools including another rust tool for general cross-compilation.

I believe this will make it harder to search for this project and examples.

For the name of the executable, single letter names like x are often used as shell aliases, e.g. g for git, k for kubectl. I've used x in the past to run a command in a separate X11 window.

I would suggest a name containing app because packaging a rust project as an app feels like the main focus of this project, with cross-compilation is a step to achieve this. And connect the name to the Rust ecosystem, e.g. cargo-app, rust-app.

@shoutmarble
Copy link

shoutmarble commented Dec 24, 2023

In the Micro-Controllers they have a working system that is like this

Install command Usage Mobile Equivalent
cargo install espflash $ espflash flash/monitor Copying to mobile or running on emulator [ x run ]
cargo install cargo-espflash $ cargo espflash flash Copying to mobile [ x run ]
cargo install cargo-espmonitor $ cargo espflash monitor Running on phone or emulator [x lldb ]
cargo install espup $ espup install Installing Android NDK, SDK, and SDKManager from Android Studio [x doctor]
cargo install cargo-generate $ cargo generate esp-rs/esp-template Generating a Mobile Wry, Diouxus, Bevy, Egui, Iced, etc [missing?]

Their could be any number of templates managed by the project itself or independently...

IPHONE ANDROID
cargo generate iphone-wry-template.git cargo generate android-wry-template.git
cargo generate iphone-diouxus-template.git cargo generate android-diouxus-template.git
cargo generate iphone-bevy-template.git cargo generate android-bevy-template.git
cargo generate iphone-egui-template.git cargo generate android-egui-template.git
cargo generate iphone-iced-template.git cargo generate android-iced-template.git

The Build and Run Cycle would be

Micro-Controller Mobile
cargo build x build
cargo espflash flash x run --device adb:123sdv
cargo espflash monitor x lldb --device adb:123sdv

We would search or make a template for our mobile platform and framework

cargo-generate templates

@shoutmarble
Copy link

shoutmarble commented Dec 26, 2023

Maybe jdx/rtx may augment x doctor/x build/x run and with environment variable setting, installing, setting up dependencies for local builds of x doctor dependencies for some windows/linux/macos users that may have to do local source builds for x doctor?

jdx/rtx with x doctor may help install some of the manual setup of installing Android/Iphone dependencies
Cargo-NDK does this already...
NDK, SDK, CMDLINETOOLS, ANDROID STUDIO

jdx/rtx
image

I only saw this project trending and thought I would mention it.

@phatblat
Copy link

FYI, rtx has been renamed to mise, probably because of the confusion with the NVidia brand and resulting un-searchability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants