From b44fbe5b1b425b8a8c23e4f0ba80583944ab303a Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Thu, 27 Oct 2022 15:09:08 +0200 Subject: manuals: use references to the "Build Directory" term Replace instances of "Build Directory" and "build directory" (when applicable) by :term:`Build Directory` as already done in most places. Doing this, fix the indentation of the paragraphs with this term. (From yocto-docs rev: dce50679242d39f133e0cde5c8483b5e69f3eb54) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/overview-manual/development-environment.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'documentation/overview-manual/development-environment.rst') diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst index 43a6f1b480..04aea1373c 100644 --- a/documentation/overview-manual/development-environment.rst +++ b/documentation/overview-manual/development-environment.rst @@ -623,11 +623,9 @@ MIT license `here `__. When you build an image using the Yocto Project, the build process uses a known list of licenses to ensure compliance. You can find this list in -the :term:`Source Directory` at -``meta/files/common-licenses``. Once the build completes, the list of -all licenses found and used during that build are kept in the -:term:`Build Directory` at -``tmp/deploy/licenses``. +the :term:`Source Directory` at ``meta/files/common-licenses``. Once the +build completes, the list of all licenses found and used during that build +are kept in the :term:`Build Directory` at ``tmp/deploy/licenses``. If a module requires a license that is not in the base list, the build process generates a warning during the build. These tools make it easier -- cgit v1.2.3-54-g00ecf