Fossil SCM
[Grammar] build.wiki changes.
Commit
3efc143294339ac780f70e9363cbcab7f0c19c20d00a4ee3b943689b03023c8b
Parent
7852e40b1b4b4ac…
1 file changed
+2
-2
+2
-2
| --- www/build.wiki | ||
| +++ www/build.wiki | ||
| @@ -55,11 +55,11 @@ | ||
| 55 | 55 | <h2>Aside: Is it really safe to use an unreleased development version of |
| 56 | 56 | the Fossil source code?</h2> |
| 57 | 57 | |
| 58 | 58 | Yes! Any check-in on the |
| 59 | 59 | [/timeline?t=trunk | trunk branch] of the Fossil |
| 60 | -[https://fossil-scm.org/ | Fossil self-hosting repository] | |
| 60 | +[https://fossil-scm.org/ | self-hosting repository] | |
| 61 | 61 | will work fine. (Dodgy code is always on a branch.) In the unlikely |
| 62 | 62 | event that you pick a version with a serious bug, it still won't |
| 63 | 63 | clobber your files. Fossil uses several |
| 64 | 64 | [./selfcheck.wiki | self-checks] prior to committing any |
| 65 | 65 | repository change that prevent loss-of-work due to bugs. |
| @@ -475,11 +475,11 @@ | ||
| 475 | 475 | environment variables which are required by <tt>emcc</tt> and will |
| 476 | 476 | fail if it cannot do so. Once it's set up the environment, it passes |
| 477 | 477 | on all of its arguments to <tt>emcc</tt>. |
| 478 | 478 | |
| 479 | 479 | The WASM-related build parts are set up such that none of them should |
| 480 | -ever trigger implicity (e.g. via dependencies resolution) in a normal | |
| 480 | +ever trigger implicitly (e.g. via dependencies resolution) in a normal | |
| 481 | 481 | build cycle. They are instead explicitly built as described below. |
| 482 | 482 | |
| 483 | 483 | From the top of the source tree, all WASM-related components can be |
| 484 | 484 | built with: |
| 485 | 485 | |
| 486 | 486 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -55,11 +55,11 @@ | |
| 55 | <h2>Aside: Is it really safe to use an unreleased development version of |
| 56 | the Fossil source code?</h2> |
| 57 | |
| 58 | Yes! Any check-in on the |
| 59 | [/timeline?t=trunk | trunk branch] of the Fossil |
| 60 | [https://fossil-scm.org/ | Fossil self-hosting repository] |
| 61 | will work fine. (Dodgy code is always on a branch.) In the unlikely |
| 62 | event that you pick a version with a serious bug, it still won't |
| 63 | clobber your files. Fossil uses several |
| 64 | [./selfcheck.wiki | self-checks] prior to committing any |
| 65 | repository change that prevent loss-of-work due to bugs. |
| @@ -475,11 +475,11 @@ | |
| 475 | environment variables which are required by <tt>emcc</tt> and will |
| 476 | fail if it cannot do so. Once it's set up the environment, it passes |
| 477 | on all of its arguments to <tt>emcc</tt>. |
| 478 | |
| 479 | The WASM-related build parts are set up such that none of them should |
| 480 | ever trigger implicity (e.g. via dependencies resolution) in a normal |
| 481 | build cycle. They are instead explicitly built as described below. |
| 482 | |
| 483 | From the top of the source tree, all WASM-related components can be |
| 484 | built with: |
| 485 | |
| 486 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -55,11 +55,11 @@ | |
| 55 | <h2>Aside: Is it really safe to use an unreleased development version of |
| 56 | the Fossil source code?</h2> |
| 57 | |
| 58 | Yes! Any check-in on the |
| 59 | [/timeline?t=trunk | trunk branch] of the Fossil |
| 60 | [https://fossil-scm.org/ | self-hosting repository] |
| 61 | will work fine. (Dodgy code is always on a branch.) In the unlikely |
| 62 | event that you pick a version with a serious bug, it still won't |
| 63 | clobber your files. Fossil uses several |
| 64 | [./selfcheck.wiki | self-checks] prior to committing any |
| 65 | repository change that prevent loss-of-work due to bugs. |
| @@ -475,11 +475,11 @@ | |
| 475 | environment variables which are required by <tt>emcc</tt> and will |
| 476 | fail if it cannot do so. Once it's set up the environment, it passes |
| 477 | on all of its arguments to <tt>emcc</tt>. |
| 478 | |
| 479 | The WASM-related build parts are set up such that none of them should |
| 480 | ever trigger implicitly (e.g. via dependencies resolution) in a normal |
| 481 | build cycle. They are instead explicitly built as described below. |
| 482 | |
| 483 | From the top of the source tree, all WASM-related components can be |
| 484 | built with: |
| 485 | |
| 486 |