manuals: use references to the "Build Directory" term
PATCH 1/1 manuals: use references to the "Build Directory" term
From: Michael Opdenacker <[email protected]>
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.
Signed-off-by Michael Opdenacker <[email protected]>
--- documentation/brief-yoctoprojectqs/index.rst | 12 +- documentation/dev-manual/common-tasks.rst | 269 ++++++++---------- documentation/dev-manual/qemu.rst | 12 +- documentation/dev-manual/start.rst | 4 +- documentation/kernel-dev/common.rst | 45 ++- documentation/kernel-dev/concepts-appx.rst | 3 +- documentation/kernel-dev/intro.rst | 4 +- documentation/kernel-dev/maint-appx.rst | 5 +- .../migration-guides/migration-1.5.rst | 7 +- .../migration-guides/migration-1.6.rst | 4 +- .../migration-guides/migration-1.7.rst | 2 +- .../migration-guides/migration-2.6.rst | 3 +- .../migration-guides/migration-general.rst | 2 +- documentation/overview-manual/concepts.rst | 74 +++-- .../development-environment.rst | 8 +- documentation/profile-manual/usage.rst | 4 +- documentation/ref-manual/classes.rst | 11 +- documentation/ref-manual/faq.rst | 17 +- documentation/ref-manual/structure.rst | 33 ++- documentation/ref-manual/terms.rst | 26 +- documentation/ref-manual/variables.rst | 63 ++-- .../sdk-manual/appendix-customizing.rst | 5 +- documentation/sdk-manual/appendix-obtain.rst | 23 +- documentation/sdk-manual/extensible.rst | 4 +- .../test-manual/understand-autobuilder.rst | 2 +- documentation/toaster-manual/reference.rst | 11 +- .../toaster-manual/setup-and-use.rst | 19 +- 27 files changed, 295 insertions(+), 377 deletions(-)
documentation/brief-yoctoprojectqs/index.rst +5 -7
@@ -224,13 +224,13 @@ an entire Linux distribution, including the toolchain, from source. Among other things, the script creates the :term:`Build Directory`, which is ``build`` in this case and is located in the :term:`Source Directory`. After - the script runs, your current working directory is set to the Build - Directory. Later, when the build completes, the Build Directory contains all the - files created during the build. + the script runs, your current working directory is set to the + :term:`Build Directory`. Later, when the build completes, the + :term:`Build Directory` contains all the files created during the build. #. **Examine Your Local Configuration File:** When you set up the build environment, a local configuration file named ``local.conf`` becomes - available in a ``conf`` subdirectory of the Build Directory. For this + available in a ``conf`` subdirectory of the :term:`Build Directory`. For this example, the defaults are set to build for a ``qemux86`` target, which is suitable for emulation. The package manager used is set to the RPM package manager.
@@ -345,9 +345,7 @@ Follow these steps to add a hardware layer: #. **Add Your Layer to the Layer Configuration File:** Before you can use a layer during a build, you must add it to your ``bblayers.conf`` - file, which is found in the - :term:`Build Directory` ``conf`` - directory. + file, which is found in the :term:`Build Directory` ``conf`` directory. Use the ``bitbake-layers add-layer`` command to add the layer to the configuration file:
documentation/dev-manual/common-tasks.rst +115 -154
568 lines not on this page · raw message
documentation/dev-manual/qemu.rst +5 -7
@@ -99,8 +99,7 @@ available. Follow these general steps to run QEMU: Here are some additional examples to help illustrate further QEMU: - This example starts QEMU with MACHINE set to "qemux86-64". - Assuming a standard - :term:`Build Directory`, ``runqemu`` + Assuming a standard :term:`Build Directory`, ``runqemu`` automatically finds the ``bzImage-qemux86-64.bin`` image file and the ``core-image-minimal-qemux86-64-20200218002850.rootfs.ext4`` (assuming the current build created a ``core-image-minimal``
@@ -246,11 +245,10 @@ be a problem when QEMU is running with KVM enabled. Specifically, software compiled with a certain CPU feature crashes when run on a CPU under KVM that does not support that feature. To work around this problem, you can override QEMU's runtime CPU setting by changing the -``QB_CPU_KVM`` variable in ``qemuboot.conf`` in the -:term:`Build Directory` ``deploy/image`` -directory. This setting specifies a ``-cpu`` option passed into QEMU in -the ``runqemu`` script. Running ``qemu -cpu help`` returns a list of -available supported CPU types. +``QB_CPU_KVM`` variable in ``qemuboot.conf`` in the :term:`Build Directory` +``deploy/image`` directory. This setting specifies a ``-cpu`` option passed +into QEMU in the ``runqemu`` script. Running ``qemu -cpu help`` returns a +list of available supported CPU types. QEMU Performance ================
documentation/dev-manual/start.rst +2 -2
@@ -558,8 +558,8 @@ your Yocto Project build host: access to external devices such as those connected through a USB port, but it automatically mounts your ``C:`` drive on ``/mnt/c/`` (and others), which you can use to share deploy artifacts to be later - flashed on hardware through Windows, but your build directory should - not reside inside this mountpoint. + flashed on hardware through Windows, but your :term:`Build Directory` + should not reside inside this mountpoint. Once you have WSL 2 set up, everything is in place to develop just as if you were running on a native Linux machine. If you are going to use the
documentation/kernel-dev/common.rst +18 -27
78 lines not on this page · raw message
documentation/kernel-dev/concepts-appx.rst +1 -2
@@ -319,8 +319,7 @@ image. The following figure shows the temporary file structure created on your host system when you build the kernel using BitBake. This -:term:`Build Directory` contains all the -source files used during the build. +:term:`Build Directory` contains all the source files used during the build. .. image:: figures/kernel-overview-2-generic.png :align: center
documentation/kernel-dev/intro.rst +2 -2
@@ -134,7 +134,7 @@ general information and references for further information. 3. *Make Changes to the Kernel Source Code if applicable:* Modifying the kernel does not always mean directly changing source files. However, if you have to do this, you make the changes to the files in the - Yocto's Build Directory if you are using ``devtool``. For more + Yocto's :term:`Build Directory` if you are using ``devtool``. For more information, see the ":ref:`kernel-dev/common:using \`\`devtool\`\` to patch the kernel`" section.
@@ -155,7 +155,7 @@ general information and references for further information. .. note:: Try to resist the temptation to directly edit an existing ``.config`` - file, which is found in the Build Directory among the source code + file, which is found in the :term:`Build Directory` among the source code used for the build. Doing so, can produce unexpected results when the OpenEmbedded build system regenerates the configuration file.
documentation/kernel-dev/maint-appx.rst +2 -3
@@ -229,6 +229,5 @@ This behavior means that all the generated files for a particular machine or BSP are now in the build tree directory. The files include the final ``.config`` file, all the ``.o`` files, the ``.a`` files, and so forth. Since each machine or BSP has its own separate -:term:`Build Directory` in its own separate -branch of the Git repository, you can easily switch between different -builds. +:term:`Build Directory` in its own separate branch of the Git repository, +you can easily switch between different builds.
documentation/migration-guides/migration-1.5.rst +3 -4
@@ -126,10 +126,9 @@ The following directory changes exist: :term:`DEPLOY_DIR_IMAGE` variable in the external environment. - When buildhistory is enabled, its output is now written under the - :term:`Build Directory` rather than - :term:`TMPDIR`. Doing so makes it easier to delete - :term:`TMPDIR` and preserve the build history. Additionally, data for - produced SDKs is now split by :term:`IMAGE_NAME`. + :term:`Build Directory` rather than :term:`TMPDIR`. Doing so makes + it easier to delete :term:`TMPDIR` and preserve the build history. + Additionally, data for produced SDKs is now split by :term:`IMAGE_NAME`. - The ``pkgdata`` directory produced as part of the packaging process has been collapsed into a single machine-specific directory. This
documentation/migration-guides/migration-1.6.rst +2 -2
@@ -233,9 +233,9 @@ Separate build and source directories have been enabled by default for selected recipes where it is known to work and for all recipes that inherit the :ref:`cmake <ref-classes-cmake>` class. In future releases the :ref:`autotools <ref-classes-autotools>` class -will enable a separate build directory by default as well. Recipes +will enable a separate :term:`Build Directory` by default as well. Recipes building Autotools-based software that fails to build with a separate -build directory should be changed to inherit from the +:term:`Build Directory` should be changed to inherit from the :ref:`autotools-brokensep <ref-classes-autotools>` class instead of the ``autotools`` or ``autotools_stage``\ classes.
documentation/migration-guides/migration-1.7.rst +1 -1
@@ -42,7 +42,7 @@ Autotools Class Changes The following :ref:`autotools <ref-classes-autotools>` class changes occurred: -- *A separate build directory is now used by default:* The +- *A separate :term:`Build Directory` is now used by default:* The :ref:`autotools <ref-classes-autotools>` class has been changed to use a directory for building (:term:`B`), which is separate from the source directory
documentation/migration-guides/migration-2.6.rst +1 -2
@@ -343,8 +343,7 @@ BitBake Changes --------------- The server logfile ``bitbake-cookerdaemon.log`` is now always placed in -the :term:`Build Directory` instead of the current -directory. +the :term:`Build Directory` instead of the current directory. .. _migration-2.6-security-changes:
documentation/migration-guides/migration-general.rst +1 -1
@@ -86,7 +86,7 @@ any new Yocto Project release. 3. Capture the buildhistory output (as specified by :term:`BUILDHISTORY_DIR`) and ensure it is preserved for subsequent builds. How you would do this depends on how you are running your builds - if you are doing this all on - one workstation in the same build directory you may not need to do + one workstation in the same :term:`Build Directory` you may not need to do anything other than not deleting the buildhistory output directory. For builds in a pipeline it may be more complicated.
documentation/overview-manual/concepts.rst +33 -41
139 lines not on this page · raw message
documentation/overview-manual/development-environment.rst +3 -5
@@ -623,11 +623,9 @@ MIT license `here <https://en.wikipedia.org/wiki/MIT_License>`__. 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
documentation/profile-manual/usage.rst +2 -2
@@ -1895,9 +1895,9 @@ manual, and boot the resulting target image. .. note:: - If you have a build directory containing multiple machines, you need + If you have a :term:`Build Directory` containing multiple machines, you need to have the MACHINE you're connecting to selected in local.conf, and - the kernel in that machine's build directory must match the kernel on + the kernel in that machine's :term:`Build Directory` must match the kernel on the booted system exactly, or you'll get the above 'crosstap' message when you try to invoke a script.
documentation/ref-manual/classes.rst +5 -6
@@ -1864,10 +1864,10 @@ package-specific classes: You can control the list of resulting package formats by using the :term:`PACKAGE_CLASSES` variable defined in your ``conf/local.conf`` configuration file, which is located in the :term:`Build Directory`. -When defining the variable, you can -specify one or more package types. Since images are generated from -packages, a packaging class is needed to enable image generation. The -first class listed in this variable is used for image generation. +When defining the variable, you can specify one or more package types. +Since images are generated from packages, a packaging class is needed +to enable image generation. The first class listed in this variable is +used for image generation. If you take the optional step to set up a repository (package feed) on the development host that can be used by DNF, you can install packages
@@ -2353,8 +2353,7 @@ recipe are no longer needed. However, by default, the build system preserves these files for inspection and possible debugging purposes. If you would rather have these files deleted to save disk space as the build progresses, you can enable :ref:`rm_work <ref-classes-rm-work>` by adding the following to -your ``local.conf`` file, which is found in the :term:`Build Directory`. -:: +your ``local.conf`` file, which is found in the :term:`Build Directory`:: INHERIT += "rm_work"
documentation/ref-manual/faq.rst +8 -9
@@ -270,7 +270,7 @@ the build environment setup script (i.e. :ref:`structure-core-script`). By default, this :term:`Build Directory` is named ``build`` but can be named anything you want. -Within the Build Directory, is the ``tmp`` directory. To remove all the +Within the :term:`Build Directory`, is the ``tmp`` directory. To remove all the build output yet preserve any source code or downloaded files from previous builds, simply remove the ``tmp`` directory.
@@ -381,14 +381,13 @@ system of that image. Thus, the build system provides a value of forth. Meanwhile, ``DESTDIR`` is a path within the :term:`Build Directory`. -However, when the recipe builds a -native program (i.e. one that is intended to run on the build machine), -that program is never installed directly to the build machine's root -file system. Consequently, the build system uses paths within the Build -Directory for ``DESTDIR``, ``bindir`` and related variables. To better -understand this, consider the following two paths (artificially broken -across lines for readability) where the first is relatively normal and -the second is not:: +However, when the recipe builds a native program (i.e. one that is +intended to run on the build machine), that program is never installed +directly to the build machine's root file system. Consequently, the build +system uses paths within the Build Directory for ``DESTDIR``, ``bindir`` +and related variables. To better understand this, consider the following +two paths (artificially broken across lines for readability) where the +first is relatively normal and the second is not:: /home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/ 1.2.8-r0/sysroot-destdir/usr/bin
documentation/ref-manual/structure.rst +16 -17
@@ -57,9 +57,8 @@ For more information on BitBake, see the :doc:`BitBake User Manual This directory contains user configuration files and the output generated by the OpenEmbedded build system in its standard configuration where the source tree is combined with the output. The :term:`Build Directory` -is created initially when you ``source`` -the OpenEmbedded build environment setup script (i.e. -:ref:`structure-core-script`). +is created initially when you ``source`` the OpenEmbedded build environment +setup script (i.e. :ref:`structure-core-script`). It is also possible to place output and configuration files in a directory separate from the :term:`Source Directory` by
@@ -153,10 +152,10 @@ BitBake commands. The script uses other scripts within the ``scripts`` directory to do the bulk of the work. When you run this script, your Yocto Project environment is set up, a -:term:`Build Directory` is created, your working -directory becomes the Build Directory, and you are presented with some -simple suggestions as to what to do next, including a list of some -possible targets to build. Here is an example:: +:term:`Build Directory` is created, your working directory becomes the +:term:`Build Directory`, and you are presented with some simple +suggestions as to what to do next, including a list of some possible +targets to build. Here is an example:: $ source oe-init-build-env
@@ -182,12 +181,13 @@ See the section in the Yocto Project Development Tasks Manual for more information. -By default, running this script without a Build Directory argument +By default, running this script without a :term:`Build Directory` argument creates the ``build/`` directory in your current working directory. If -you provide a Build Directory argument when you ``source`` the script, -you direct the OpenEmbedded build system to create a Build Directory of -your choice. For example, the following command creates a Build -Directory named ``mybuilds/`` that is outside of the :term:`Source Directory`:: +you provide a :term:`Build Directory` argument when you ``source`` the script, +you direct the OpenEmbedded build system to create a :term:`Build Directory` of +your choice. For example, the following command creates a +:term:`Build Directory` named ``mybuilds/`` that is outside of the +:term:`Source Directory`:: $ source oe-init-build-env ~/mybuilds
@@ -219,11 +219,10 @@ These files are standard top-level files. The Build Directory --- ``build/`` ================================== -The OpenEmbedded build system creates the :term:`Build Directory` -when you run the build environment setup -script :ref:`structure-core-script`. If you do not give the Build -Directory a specific name when you run the setup script, the name -defaults to ``build/``. +The OpenEmbedded build system creates the :term:`Build Directory` when you run +the build environment setup script :ref:`structure-core-script`. If you do not +give the :term:`Build Directory` a specific name when you run the setup script, +the name defaults to ``build/``. For subsequent parsing and processing, the name of the Build directory is available via the :term:`TOPDIR` variable.
documentation/ref-manual/terms.rst +13 -13
@@ -64,31 +64,31 @@ universal, the list includes them just in case: builds. The area is created when you ``source`` the setup environment script that is found in the Source Directory (i.e. :ref:`ref-manual/structure:\`\`oe-init-build-env\`\``). The - :term:`TOPDIR` variable points to the Build Directory. + :term:`TOPDIR` variable points to the :term:`Build Directory`. - You have a lot of flexibility when creating the Build Directory. + You have a lot of flexibility when creating the :term:`Build Directory`. Following are some examples that show how to create the directory. The examples assume your :term:`Source Directory` is named ``poky``: - - Create the Build Directory inside your Source Directory and let - the name of the Build Directory default to ``build``: + - Create the :term:`Build Directory` inside your Source Directory and let + the name of the :term:`Build Directory` default to ``build``: .. code-block:: shell $ cd poky $ source oe-init-build-env - - Create the Build Directory inside your home directory and + - Create the :term:`Build Directory` inside your home directory and specifically name it ``test-builds``: .. code-block:: shell $ source poky/oe-init-build-env test-builds - - Provide a directory path and specifically name the Build - Directory. Any intermediate folders in the pathname must exist. - This next example creates a Build Directory named - ``YP-&DISTRO;`` within the existing directory ``mybuilds``: + - Provide a directory path and specifically name the + :term:`Build Directory`. Any intermediate folders in the pathname + must exist. This next example creates a :term:`Build Directory` + named ``YP-&DISTRO;`` within the existing directory ``mybuilds``: .. code-block:: shell
@@ -96,13 +96,13 @@ universal, the list includes them just in case: .. note:: - By default, the Build Directory contains :term:`TMPDIR`, which is a + By default, the :term:`Build Directory` contains :term:`TMPDIR`, which is a temporary directory the build system uses for its work. :term:`TMPDIR` cannot - be under NFS. Thus, by default, the Build Directory cannot be under - NFS. However, if you need the Build Directory to be under NFS, you can + be under NFS. Thus, by default, the :term:`Build Directory` cannot be under + NFS. However, if you need the :term:`Build Directory` to be under NFS, you can set this up by setting :term:`TMPDIR` in your ``local.conf`` file to use a local drive. Doing so effectively separates :term:`TMPDIR` from :term:`TOPDIR`, which is the - Build Directory. + :term:`Build Directory`. :term:`Build Host` The system used to build images in a Yocto Project Development
documentation/ref-manual/variables.rst +28 -35
147 lines not on this page · raw message
documentation/sdk-manual/appendix-customizing.rst +2 -3
@@ -286,9 +286,8 @@ source, you need to do a number of things: ESDK_LOCALCONF_ALLOW = "SSTATE_MIRRORS" - Alternatively, if you just want to set the :term:`SSTATE_MIRRORS` - variable's value for the SDK alone, create a - ``conf/sdk-extra.conf`` file either in your - :term:`Build Directory` or within any + variable's value for the SDK alone, create a ``conf/sdk-extra.conf`` + file either in your :term:`Build Directory` or within any layer and put your :term:`SSTATE_MIRRORS` setting within that file. .. note::
documentation/sdk-manual/appendix-obtain.rst +10 -13
@@ -116,24 +116,21 @@ build the SDK installer. Follow these steps: $ source oe-init-build-env - Among other things, the script - creates the :term:`Build Directory`, - which is - ``build`` in this case and is located in the Source Directory. After - the script runs, your current working directory is set to the - ``build`` directory. + Among other things, the script creates the :term:`Build Directory`, which + is ``build`` in this case and is located in the Source Directory. After + the script runs, your current working directory is set to the ``build`` + directory. 4. *Make Sure You Are Building an Installer for the Correct Machine:* - Check to be sure that your - :term:`MACHINE` variable in the - ``local.conf`` file in your Build Directory matches the architecture + Check to be sure that your :term:`MACHINE` variable in the ``local.conf`` + file in your :term:`Build Directory` matches the architecture for which you are building. 5. *Make Sure Your SDK Machine is Correctly Set:* If you are building a toolchain designed to run on an architecture that differs from your current development host machine (i.e. the build host), be sure that - the :term:`SDKMACHINE` variable - in the ``local.conf`` file in your Build Directory is correctly set. + the :term:`SDKMACHINE` variable in the ``local.conf`` file in your + :term:`Build Directory` is correctly set. .. note::
@@ -164,7 +161,7 @@ build the SDK installer. Follow these steps: that matches your target root filesystem. When the ``bitbake`` command completes, the SDK installer will be in - ``tmp/deploy/sdk`` in the Build Directory. + ``tmp/deploy/sdk`` in the :term:`Build Directory`. .. note::
@@ -181,7 +178,7 @@ build the SDK installer. Follow these steps: libc-staticdev" 7. *Run the Installer:* You can now run the SDK installer from - ``tmp/deploy/sdk`` in the Build Directory. Following is an example:: + ``tmp/deploy/sdk`` in the :term:`Build Directory`. Following is an example:: $ cd poky/build/tmp/deploy/sdk $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
documentation/sdk-manual/extensible.rst +2 -2
@@ -64,7 +64,7 @@ binary artefact cache over the network for developers with underpowered laptops. Setting up the Extensible SDK environment directly in a Yocto build ------------------------------------------------------------------- -1. Set up all the needed layers and a Yocto build directory, e.g. a regular Yocto +1. Set up all the needed layers and a Yocto :term:`Build Directory`, e.g. a regular Yocto build where ``bitbake`` can be executed. 2. Run:
@@ -175,7 +175,7 @@ Once you have the SDK installed, you must run the SDK environment setup script before you can actually use the SDK. When using a SDK directly in a Yocto build, you will find the script in -``tmp/deploy/images/qemux86-64/`` in your build directory. +``tmp/deploy/images/qemux86-64/`` in your :term:`Build Directory`. When using a standalone SDK installer, this setup script resides in the directory you chose when you installed the SDK, which is either the
documentation/test-manual/understand-autobuilder.rst +1 -1
@@ -242,7 +242,7 @@ of post-build steps, including: #. Call ``scripts/upload-error-reports`` to send any error reports generated to the remote server. -#. Cleanup the build directory using +#. Cleanup the :term:`Build Directory` using :ref:`test-manual/understand-autobuilder:clobberdir` if the build was successful, else rename it to "build-renamed" for potential future debugging.
documentation/toaster-manual/reference.rst +5 -6
@@ -522,14 +522,13 @@ tasks. You can locate these commands in the - When using ``manage.py`` commands given a default configuration, you must be sure that your working directory is set to the - :term:`Build Directory`. Using - ``manage.py`` commands from the Build Directory allows Toaster to - find the ``toaster.sqlite`` file, which is located in the Build - Directory. + :term:`Build Directory`. Using ``manage.py`` commands from the + :term:`Build Directory` allows Toaster to find the ``toaster.sqlite`` + file, which is located in the :term:`Build Directory`. - For non-default database configurations, it is possible that you can use ``manage.py`` commands from a directory other than the - Build Directory. To do so, the ``toastermain/settings.py`` file + :term:`Build Directory`. To do so, the ``toastermain/settings.py`` file must be configured to point to the correct database backend. ``buildslist``
@@ -549,7 +548,7 @@ database. You need to run the ``buildslist`` command first to identify existing builds in the database before using the :ref:`toaster-manual/reference:\`\`builddelete\`\`` command. Here is an -example that assumes default repository and build directory names: +example that assumes default repository and :term:`Build Directory` names: .. code-block:: shell
documentation/toaster-manual/setup-and-use.rst +9 -10
@@ -23,8 +23,8 @@ Once in that directory, source the build environment script:: $ source oe-init-build-env -Next, from the build directory (e.g. -``poky/build``), start Toaster using this command:: +Next, from the :term:`Build Directory` (e.g. ``poky/build``), start Toaster +using this command:: $ source toaster start
@@ -124,14 +124,14 @@ causes Toaster to create and use ``$TOASTER_DIR./_toaster_clones``. The Build Directory =================== -Toaster creates a build directory within your Source Directory (e.g. +Toaster creates a :term:`Build Directory` within your Source Directory (e.g. ``poky``) to execute the builds. Alternatively, if you would like all of your Toaster related files and directories to be in a particular location, you can set the ``TOASTER_DIR`` environment variable, which takes precedence over your current working directory. Setting this environment variable causes -Toaster to use ``$TOASTER_DIR/build`` as the build directory. +Toaster to use ``$TOASTER_DIR/build`` as the :term:`Build Directory`. Creating a Django Superuser ===========================
@@ -152,8 +152,8 @@ superuser by following these steps: $ export PATH=$PATH:$HOME/.local/bin #. From the directory containing the Toaster database, which by default - is the :term:`Build Directory`, - invoke the ``createsuperuser`` command from ``manage.py``:: + is the :term:`Build Directory`, invoke the ``createsuperuser`` command from + ``manage.py``:: $ cd poky/build $ ../bitbake/lib/toaster/manage.py createsuperuser
@@ -179,7 +179,7 @@ example, if you are running Toaster locally, use the following URL:: http://127.0.0.1:8000/admin You can use the Django administration interface to set Toaster configuration -parameters such as the build directory, layer sources, default variable +parameters such as the :term:`Build Directory`, layer sources, default variable values, and BitBake versions. Setting Up a Production Instance of Toaster
@@ -317,8 +317,7 @@ Perform the following steps to install Toaster: the ":ref:`toaster-manual/reference:Configuring Toaster`" section. This line also runs the ``checksettings`` command, which configures - the location of the Toaster :term:`Build Directory`. - The Toaster + the location of the Toaster :term:`Build Directory`. The Toaster root directory ``TOASTER_DIR`` determines where the Toaster build directory is created on the file system. In the example above, ``TOASTER_DIR`` is set as follows::
@@ -326,7 +325,7 @@ Perform the following steps to install Toaster: /var/www/toaster/poky - This setting causes the Toaster build directory to be:: + This setting causes the Toaster :term:`Build Directory` to be:: /var/www/toaster/poky/build
Signature · 1 line
2.34.1