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

Support other cargo wrappers with bevy build/run #71

Open
TimJentzsch opened this issue Sep 14, 2024 · 5 comments
Open

Support other cargo wrappers with bevy build/run #71

TimJentzsch opened this issue Sep 14, 2024 · 5 comments
Labels
A-Cross-Cutting Affects multiple areas of the repository C-Enhancement A general improvement

Comments

@TimJentzsch
Copy link
Collaborator

Can this run another binary than cargo? On Windows, you need to run cargo-clif in order to use cranelift.

Originally posted by @janhohenheim in #24 (comment)

@janhohenheim janhohenheim added C-Enhancement A general improvement A-Cross-Cutting Affects multiple areas of the repository labels Sep 14, 2024
@janhohenheim
Copy link
Member

Also important for cargo-mommy, of course ~

@BD103
Copy link
Member

BD103 commented Sep 14, 2024

I feel like environmental variables best fit this use-case. Maybe something like BEVY_CLI_CARGO=/path/to/cargo?

@janhohenheim
Copy link
Member

While we are on it, we could also specify another path for rustup. I don't know any use-case for that though.

@BD103
Copy link
Member

BD103 commented Sep 14, 2024

While we are on it, we could also specify another path for rustup. I don't know any use-case for that though.

This could be useful if:

  1. You're a rustup developer and have multiple instance installed.
  2. You installed rustup in a custom way, making it not always on the PATH.

I would like all of these environmental variables documented, though. Perhaps through bevy --help or a man page?

@janhohenheim
Copy link
Member

Update for others reading this: Tim already implemented the rustup env var as BEVY_CLI_RUSTUP :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Cross-Cutting Affects multiple areas of the repository C-Enhancement A general improvement
Projects
None yet
Development

No branches or pull requests

3 participants