From 0ffd4bd8a2710a037542698bc22ec9f08417d9f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Klaim=20=28Jo=C3=ABl=20Lamotte=29?= <142265+Klaim@users.noreply.github.com> Date: Fri, 30 May 2025 06:26:51 +0200 Subject: [PATCH] fixed typo and improved wording MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Klaim (Joël Lamotte) <142265+Klaim@users.noreply.github.com> --- docs/mkdocs/docs/integration/package_managers.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/mkdocs/docs/integration/package_managers.md b/docs/mkdocs/docs/integration/package_managers.md index 3978166eb..91d38db53 100644 --- a/docs/mkdocs/docs/integration/package_managers.md +++ b/docs/mkdocs/docs/integration/package_managers.md @@ -717,7 +717,7 @@ Note: [`build2`](https://build2.org) should not be considered as a standalone pa To use this package in an exising [`build2`](https://build2.org) project, the general steps are: - 1.
Make the package available to download from a package repository that provides it. + 1.
Make the package available to download from a package repository that provides it. Your project's `repositories.manifest` specifies where the package manager will try to acquire packages by default. Make sure one of the repositories specified in this file provides `nlhomann-json` package. The recommended open-source repository is [`cppget.org`](https://cppget.org/). @@ -732,7 +732,7 @@ To use this package in an exising [`build2`](https://build2.org) project, the ge 2.
Add this package as dependency of your project. - In your project's `manifest` add the dependency to the package, like `depends: nlohmann-json`. You could also add some [version constraints](https://build2.org/build2-toolchain/doc/build2-toolchain-intro.xhtml#guide-add-remove-deps). + In your project's `manifest` add the dependency to the package using `depends: nlohmann-json`. You could also add some [version constraints](https://build2.org/build2-toolchain/doc/build2-toolchain-intro.xhtml#guide-add-remove-deps). For example, to depend on the latest version available: ``` depends: nlohmann-json @@ -747,7 +747,7 @@ To use this package in an exising [`build2`](https://build2.org) project, the ge ``` import nljson = nlhomann-json%lib{json} ``` - - add the library's target as requirement for your target using it, for example: + - then add the library's target as requirement for your target using it, for example: ``` exe{example} : ... $nljson ``` @@ -757,7 +757,7 @@ To use this package in an exising [`build2`](https://build2.org) project, the ge At this point, assuming your project is initialized in a build-configuration, any `b` or `bdep update` command that will update/build the project will also acquire the missing dependency automatically, then build it and link it with your target. - If you just want to trigger the dependencies synchronization for all your configurations: + If you just want to synchronize dependencies for all your configurations to download the ones you just added: ``` bdep sync -af ``` @@ -812,10 +812,10 @@ To use this package in an exising [`build2`](https://build2.org) project, the ge # create default C/C++ build configuration in ../example-myconfig/, initialize the project in it (downloads it's dependencies in it too) bdep init -C @myconfig cc - # build only + # build only, b - # build and test the executable's output, will only work if the `tescript` is correct + # or build and test the executable's output, will only work if the `tescript` is correct b test ```