|
|
@@ -51,13 +51,16 @@ contributions.
|
|
|
In order to set up a machine and git repository for developing on Carbon, a
|
|
|
typical tool setup flow is:
|
|
|
|
|
|
+<!-- google-doc-style-ignore -->
|
|
|
+<!-- Need to retain "repo" in "gh repo clone". -->
|
|
|
+
|
|
|
1. Install [package managers](#package-managers).
|
|
|
2. Install [main tools](#main-tools) and any desired
|
|
|
[optional tools](#optional-tools).
|
|
|
3. Set up the [git](https://git-scm.com/) repository:
|
|
|
- In GitHub, create a fork for development at
|
|
|
https://github.com/carbon-language/carbon-lang.
|
|
|
- - `gh repository clone USER/carbon-lang`, or otherwise clone the fork.
|
|
|
+ - `gh repo clone USER/carbon-lang`, or otherwise clone the fork.
|
|
|
- `cd carbon-lang` to go into the cloned fork's directory.
|
|
|
- `git submodule update --init --depth=1` to sync submodules if you'll be
|
|
|
building c++ code or working on the compiler.
|
|
|
@@ -67,6 +70,8 @@ typical tool setup flow is:
|
|
|
4. Validate your installation by invoking `bazel test //...:all' from the
|
|
|
project root. All tests should pass.
|
|
|
|
|
|
+<!-- google-doc-style-resume -->
|
|
|
+
|
|
|
## Package managers
|
|
|
|
|
|
Instructions for installing tools can be helpful for installing tooling. These
|
Jon Meow