@@ -86,17 +86,17 @@ Only nine dependency types matter in practice:
8686
8787#### Possible dependency types {#possible-dependency-types}
8888
89−| Dependency type | Dependency’s host platform | Dependency’s target platform |
90−|---------------------|----------------------------|------------------------------|
91−| build→ * | build | (none) |
92−| build→ build | build | build |
93−| build→ host | build | host |
94−| build→ target | build | target |
95−| host→ * | host | (none) |
96−| host→ host | host | host |
97−| host→ target | host | target |
98−| target→ * | target | (none) |
99−| target→ target | target | target |
89+| Dependency type | Dependency’s host platform | Dependency’s target platform |
90+|-----------------|----------------------------|------------------------------|
91+| build → * | build | (none) |
92+| build → build | build | build |
93+| build → host | build | host |
94+| build → target | build | target |
95+| host → * | host | (none) |
96+| host → host | host | host |
97+| host → target | host | target |
98+| target → * | target | (none) |
99+| target → target | target | target |
100100
101101Let's use `g++` as an example to make this table clearer. `g++` is a C++ compiler written in C. Suppose we are building `g++` with a `(build, host, target)` platform triple of `(foo, bar, baz)`. This means we are using a `foo`-machine to build a copy of `g++` which will run on a `bar`-machine and emit binaries for the `baz`-machine.
102102