-
Notifications
You must be signed in to change notification settings - Fork 13.4k
x.py setup
could detect llvm-config
in the user's path and propose to set it
#77579
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
x.py setup
x.py setup
could detect llvm-config
in the user's path and propose to set it
I would like to suggest |
FWIW if you have a windows machine, looking into making download-ci-llvm work would be amazing, and likely benefit everyone using Windows since it'd "just work" presumably. I still need to find time to investigate on a mac (which I do have ready access to). |
I'm on Linux, unfortunately, and don't have easy access to a Windows machine. I'll keep that in mind though :) |
@jyn514 so on linux, do you want the setup to ask the user whether they want to use the CI-built llvm, or build their own? Or just add a |
The templates in Personally I think I'd always set |
I would be onboard with adding a download-ci-llvm = "if-available" or something like that; we can check if we're on x86_64-unknown-linux-gnu and use it then. |
Detect configuration for LLVM during setup This is a first draft to address rust-lang#77579, setting `download-ci-llvm` to true on Linux, but I could also implement the `if-available` setting mentioned in the issue. On other platforms I was thinking about using [the which crate](https://crates.io/crates/which), if adding a dependency on it is considered okay of course, to detect the presence of `llvm-config` in the path, and use it if found. Still a work in progress of course.
I'm going to close this, download-ci-llvm should be working on every tier 1 platform and I'd rather recommend that than system llvm. |
Uh oh!
There was an error while loading. Please reload this page.
New contributors might not necessarily need to recompile LLVM from scratch, especially if they already have a version on their system.
The setup script could detect the presence of
llvm-config
in the path and propose to set it automatically (this is common advice from here https://rustc-dev-guide.rust-lang.org/building/suggested.html#skipping-llvm-build)The text was updated successfully, but these errors were encountered: