diff options
| author | Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com> | 2024-05-27 10:35:05 +0200 |
|---|---|---|
| committer | Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com> | 2024-06-26 12:11:19 +0200 |
| commit | e1c182c7517be4f69a29a7b8f192ec2c9c379b75 (patch) | |
| tree | 89f95a9588256b655893035cb565c1f21865ead2 /doc | |
| parent | c55c9afbc665dce2cba7cc16561e880f56d8108b (diff) | |
| download | justbuild-e1c182c7517be4f69a29a7b8f192ec2c9c379b75.tar.gz | |
tutorials: Fix small typos
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tutorial/cross-compiling.md | 2 | ||||
| -rw-r--r-- | doc/tutorial/third-party-software.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/tutorial/cross-compiling.md b/doc/tutorial/cross-compiling.md index 43296400..50b01cd1 100644 --- a/doc/tutorial/cross-compiling.md +++ b/doc/tutorial/cross-compiling.md @@ -13,7 +13,7 @@ Cross compiling using the CC rules ---------------------------------- The `C` and `C++` rules that come with the `justbuild` repository -already have cross-compiling already built into the tool-chain +already have cross-compiling already built into the toolchain definitions for the `"gnu"` and `"clang"` compiler families; as different compilers expect different ways to be told about the target architecture, cross compiling is not supported for the `"unknown"` diff --git a/doc/tutorial/third-party-software.md b/doc/tutorial/third-party-software.md index 7b435b2b..bc8c8103 100644 --- a/doc/tutorial/third-party-software.md +++ b/doc/tutorial/third-party-software.md @@ -240,7 +240,7 @@ $ Employing high-level target caching ----------------------------------- -The make use of high-level target caching for exported targets, we need +To make use of high-level target caching for exported targets, we need to ensure that all inputs to an export target are transitively content-fixed. This is automatically the case for `"type":"git"` repositories. However, the `libfmt` repository also depends on @@ -499,7 +499,7 @@ staging mechanism the logical repository it belongs to is rooted in the ``` However, even specifying all the include locations and headers can -be tedious and in the end, it is information that `pkg-config` can +be tedious and, in the end, it is information that `pkg-config` can provide as well. So there is a rule to import libraries that way and the actual packaging-build version of `libfmt`, as provided in `etc/import.pkgconfig`, looks as follows. |