mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-09-24 18:50:09 +01:00
Jon Ross-Perkins
605763d62d
The main motivation for this is to get python loads in using the `native-py` lint fix. However, enabling that made me wonder, maybe we should fix in general? `native-cc` is delayed, but not wholly cancelled (and `native-py` picking up might indicate `native-cc` won't be too far behind). There's also some automated fixes for `.append` and dict sorting -- this felt okay to me, maybe not something to eagerly add but probably not worth stopping buildifier from fixing (I've noticed the warnings in the past and had been ignoring them). Running everything does mean that load orders are sorted automatically now, which I think is a positive. Most generally, I think these fixes aren't _harmful_, and having them done automatically seems beneficial: my biggest concern about `native-py` and `native-cc` was actually that regressions wouldn't be caught, but this addresses that issue automatically.
Local installer
This installs carbon-explorer locally for experimental use on Mac/Linux. It's not recommended for most users. Bear in mind that Carbon Language is experimental and still has no compiler. See our project status for more information.
To install to /usr, run:
bazel run -c opt //installers/local:install
To use a custom install path, run:
bazel run -c opt //installers/local:install \
--//installers/local:install_path=/my/path
To uninstall, run:
bazel run //installers/local:uninstall
The build mode is important for installs, as debug versions may be installed. It is not relevant for uninstalls.
If a custom install path is passed to :install, the same should be passed to :uninstall.
Note this is just scripting paths: it's not intended to be a full-fledged install.