From 74bf586c940d20fc5546a60a290545c7c0edecb0 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 13 Jun 2017 17:47:10 -0700 Subject: documentation: Fixed links for "build-directory" term. Fixes [YOCTO #11630] Moving the "Yocto Project Terms" section from the dev-manual to the ref-manual broke several links to the id "build-directory". I fixed these to reference into the ref-manual now. (From yocto-docs rev: debe2ae8ce203ebe0f1cee0de54124c15df8bb7e) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/bsp-guide/bsp.xml | 2 +- .../dev-manual/dev-manual-common-tasks.xml | 59 ++++++++++++---------- documentation/dev-manual/dev-manual-model.xml | 15 +++--- documentation/dev-manual/dev-manual-newbie.xml | 4 +- documentation/dev-manual/dev-manual-qemu.xml | 2 +- documentation/dev-manual/dev-manual-start.xml | 2 +- documentation/kernel-dev/kernel-dev-maint-appx.xml | 2 +- documentation/ref-manual/closer-look.xml | 10 ++-- documentation/ref-manual/faq.xml | 5 +- documentation/ref-manual/introduction.xml | 2 +- documentation/ref-manual/migration.xml | 2 +- documentation/ref-manual/ref-classes.xml | 4 +- documentation/ref-manual/ref-devtool-reference.xml | 2 +- documentation/ref-manual/ref-structure.xml | 13 ++--- documentation/ref-manual/ref-variables.xml | 56 ++++++++++---------- documentation/ref-manual/technical-details.xml | 4 +- documentation/ref-manual/usingpoky.xml | 13 ++--- .../sdk-manual/sdk-appendix-customizing.xml | 2 +- documentation/sdk-manual/sdk-appendix-mars.xml | 8 +-- documentation/sdk-manual/sdk-intro.xml | 2 +- documentation/sdk-manual/sdk-working-projects.xml | 8 +-- .../toaster-manual/toaster-manual-reference.xml | 2 +- .../toaster-manual-setup-and-use.xml | 4 +- .../yocto-project-qs/yocto-project-qs.xml | 2 +- 24 files changed, 117 insertions(+), 108 deletions(-) (limited to 'documentation') diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 0dcc65b767..9226e5cdd4 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -98,7 +98,7 @@ This root is what you add to the BBLAYERS variable in the conf/bblayers.conf file found in the - Build Directory, + Build Directory, which is established after you run one of the OpenEmbedded build environment setup scripts (i.e. &OE_INIT_FILE; diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 4a7306fb24..d73b663250 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -655,7 +655,7 @@ BBLAYERS variable in your conf/bblayers.conf file, which is found in the - Build Directory. + Build Directory. The following example shows how to enable a layer named meta-mylayer: @@ -1192,7 +1192,7 @@ from within a recipe and using EXTRA_IMAGE_FEATURES from within your local.conf file, which is found in the - Build Directory. + Build Directory. @@ -1539,7 +1539,7 @@ To run the tool, you just need to be in your - Build Directory + Build Directory and have sourced the build environment setup script (i.e. oe-init-build-env @@ -2027,7 +2027,7 @@ or oe-init-build-env-memres) and you are in the - Build Directory, + Build Directory, use BitBake to process your recipe. All you need to provide is the basename of the recipe as described @@ -4238,7 +4238,7 @@ combination of multiple libraries you want to build. You accomplish this through your local.conf configuration file in the - Build Directory. + Build Directory. An example configuration would be as follows: MACHINE = "qemux86-64" @@ -4314,7 +4314,7 @@ A unique architecture is defined for the Multilib packages, along with creating a unique deploy folder under tmp/deploy/rpm in the - Build Directory. + Build Directory. For example, consider lib32 in a qemux86-64 image. The possible architectures in the system are "all", "qemux86_64", @@ -4858,7 +4858,7 @@ or oe-init-build-env-memres) found in the - Build Directory. + Build Directory. @@ -4948,7 +4948,7 @@ or oe-init-build-env-memres script found in the - Build Directory. + Build Directory.
@@ -5934,7 +5934,7 @@ or oe-init-build-env-memres script found in the - Build Directory. + Build Directory. You must also be sure of the state of your build in the Source Directory. The following commands run menuconfig @@ -6104,7 +6104,7 @@ placed where the OpenEmbedded build system can find and apply them. Syntactically, the configuration statement is identical to what would appear in the .config file, which is in the - Build Directory: + Build Directory: tmp/work/arch-poky-linux/linux-yocto-release_specific_string/linux-arch-build_type @@ -6390,9 +6390,11 @@ machine in a Source Directory named poky. - Furthermore, the Build Directory is - build and is located in poky and - the kernel is based on the Linux 3.4 kernel. + Furthermore, the + Build Directory + is build and is located in + poky and the kernel is based on the + Linux 3.4 kernel. @@ -6593,7 +6595,7 @@ Build for the correct target architecture: Your selected MACHINE definition within the local.conf file in the - Build Directory + Build Directory specifies the target architecture used when building the Linux kernel. By default, MACHINE is set to qemux86, which specifies a 32-bit @@ -6653,7 +6655,7 @@ Never remove any files by hand from the tmp/deploy directory inside the - Build Directory. + Build Directory. Always use the various BitBake clean tasks to clear out previous build artifacts. For information on the clean tasks, see the @@ -7018,7 +7020,7 @@ previous bulleted item. Point to Your distribution configuration file: In your local.conf file in the - Build Directory, + Build Directory, set your DISTRO variable to point to your distribution's configuration file. @@ -7078,7 +7080,7 @@ TEMPLATECONF to locate the directory from which it gathers configuration information that ultimately ends up in the - Build Directory's + Build Directory conf directory. By default, TEMPLATECONF is set as follows in the poky repository: @@ -8031,7 +8033,7 @@ setting PRSERV_HOST in your local.conf file in the - Build Directory: + Build Directory: PRSERV_HOST = "localhost:0" @@ -8567,7 +8569,7 @@ Open the local.conf file inside your - Build Directory + Build Directory (e.g. ~/poky/build/conf/local.conf). @@ -9025,7 +9027,7 @@ and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the - Build Directory: + Build Directory: DISTRO_FEATURES_append = " ptest" EXTRA_IMAGE_FEATURES += "ptest-pkgs" @@ -9261,8 +9263,8 @@ By default, the OpenEmbedded build system uses the - Build Directory when - building source code. + Build Directory + when building source code. The build process involves fetching the source files, unpacking them, and then patching them if necessary before the build takes place. @@ -9626,7 +9628,7 @@ Using either of the following statements in your image recipe or from within the local.conf file found in the - Build Directory + Build Directory causes the build system to create a read-only root filesystem: IMAGE_FEATURES = "read-only-rootfs" @@ -10220,7 +10222,7 @@ TEST_IMAGE variable to "1" in your local.conf file in the - Build Directory: + Build Directory: TEST_IMAGE = "1" @@ -10352,7 +10354,8 @@ $ bitbake image -c testexport Exporting the tests places them in the - Build Directory in + Build Directory + in tmp/testexport/image, which is controlled by the TEST_EXPORT_DIR variable. @@ -11509,7 +11512,7 @@ release just the source as a tarball. You can do this by adding the following to the local.conf file found in the - Build Directory: + Build Directory: INHERIT += "archiver" ARCHIVER_MODE[src] = "original" @@ -11724,7 +11727,7 @@ report-error class by adding the following statement to the end of your local.conf file in your - Build Directory. + Build Directory. INHERIT += "report-error" @@ -11783,7 +11786,7 @@ To disable the error reporting feature, simply remove or comment out the following statement from the end of your local.conf file in your - Build Directory. + Build Directory. INHERIT += "report-error" diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 0782f0acdb..068fd66893 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -87,7 +87,8 @@ For a brief list of terms used when describing the development process in the Yocto Project, - see the "Yocto Project Terms" section. + see the + "Yocto Project Terms" section. @@ -431,8 +432,8 @@ The following figure shows the temporary file structure created on your host system when the build occurs. This - Build Directory contains all the - source files used during the build. + Build Directory + contains all the source files used during the build. @@ -478,7 +479,7 @@ Establish the temporary kernel source files: Temporary kernel source files are kept in the - Build Directory + Build Directory created by the OpenEmbedded build system when you run BitBake. If you have never built the kernel in which you are @@ -1270,7 +1271,7 @@ Find the Source Code: Temporary source code used by the OpenEmbedded build system is kept in the - Build Directory. + Build Directory. See the "Finding Temporary Source Code" section to learn how to locate the directory that has the @@ -1364,8 +1365,8 @@ experiment a bit to figure out your solution. After you have initially built the package, you can iteratively tweak the source code, which is located in the - Build Directory, and then - you can force a re-compile and quickly test your altered code. + Build Directory, + and then you can force a re-compile and quickly test your altered code. Once you settle on a solution, you can then preserve your changes in the form of patches. If you are using Quilt for development, see the diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 350c6e49a8..5a3e3ea107 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -526,8 +526,8 @@ meta/files/common-licenses. Once the build completes, the list of all licenses found and used during that build are kept in the - Build Directory at - tmp/deploy/licenses. + Build Directory + at tmp/deploy/licenses. diff --git a/documentation/dev-manual/dev-manual-qemu.xml b/documentation/dev-manual/dev-manual-qemu.xml index 41c18298a5..80e4b24ccb 100644 --- a/documentation/dev-manual/dev-manual-qemu.xml +++ b/documentation/dev-manual/dev-manual-qemu.xml @@ -252,7 +252,7 @@ qemux86" or "qemux86-64". This example starts QEMU with MACHINE set to "qemux86". Assuming a standard - Build Directory, + Build Directory, runqemu automatically finds the bzImage-qemux86.bin image file and the diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 0e335e28fc..6b97c52ada 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -309,7 +309,7 @@ Optionally ensure the conf/local.conf configuration file, which is found in the - Build Directory, + Build Directory, is set up how you want it. This file defines many aspects of the build environment including the target machine architecture through the diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.xml b/documentation/kernel-dev/kernel-dev-maint-appx.xml index 6bb0cf6fd0..7cfcb45c94 100644 --- a/documentation/kernel-dev/kernel-dev-maint-appx.xml +++ b/documentation/kernel-dev/kernel-dev-maint-appx.xml @@ -209,7 +209,7 @@ 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 - Build Directory + Build Directory in its own separate branch of the Git repository, you can easily switch between different builds. diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index c0f1747961..e4a2a022a7 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -114,7 +114,7 @@ Sourcing the build environment script creates a - Build Directory + Build Directory if one does not already exist. BitBake uses the Build Directory for all its work during builds. The Build Directory has a conf directory that @@ -641,7 +641,7 @@ When the OpenEmbedded build system generates an image or an SDK, it gets the packages from a package feed area located in the - Build Directory. + Build Directory. The general Yocto Project Development Environment figure shows this package feeds area in the upper-right corner. @@ -770,7 +770,7 @@ depend on it are re-executed. By default, everything is accomplished in the - Build Directory, + Build Directory, which has a defined structure. For additional general information on the Build Directory, see the @@ -1430,7 +1430,7 @@ Images are written out to the - Build Directory + Build Directory inside the tmp/deploy/images/machine/ folder as shown in the figure. This folder contains any files expected to be loaded on the @@ -1545,7 +1545,7 @@ Once built, the SDK installers are written out to the deploy/sdk folder inside the - Build Directory + Build Directory as shown in the figure at the beginning of this section. Depending on the type of SDK, several variables exist that help configure these files. diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index cdbdd4da24..c4b860b1ce 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -702,7 +702,8 @@ &OE_INIT_FILE; or oe-init-build-env-memres). - By default, this Build Directory + By default, this + Build Directory is named build but can be named anything you want. @@ -765,7 +766,7 @@ Meanwhile, DESTDIR is a path within the - Build Directory. + 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 diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml index deaac033a3..7f6729db55 100644 --- a/documentation/ref-manual/introduction.xml +++ b/documentation/ref-manual/introduction.xml @@ -953,7 +953,7 @@ .sh file that installs the tools in the tmp/deploy/sdk subdirectory of the - Build Directory. + Build Directory. The installer file has the string "buildtools" in the name. diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 0513b219cd..5c700bc5ea 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -821,7 +821,7 @@ When buildhistory is enabled, its output is now written under the - Build Directory + Build Directory rather than TMPDIR. Doing so makes it easier to delete diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 2b5cb88efd..472215c25a 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -2393,7 +2393,7 @@ This check was removed for YP 2.3 release PACKAGE_CLASSES variable defined in your conf/local.conf configuration file, which is located in the - Build Directory. + 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. @@ -2988,7 +2988,7 @@ This check was removed for YP 2.3 release as the build progresses, you can enable rm_work by adding the following to your local.conf file, which is found in the - Build Directory. + Build Directory. INHERIT += "rm_work" diff --git a/documentation/ref-manual/ref-devtool-reference.xml b/documentation/ref-manual/ref-devtool-reference.xml index 99d5a52a0f..64db00e714 100644 --- a/documentation/ref-manual/ref-devtool-reference.xml +++ b/documentation/ref-manual/ref-devtool-reference.xml @@ -573,7 +573,7 @@ Use the devtool create-workspace command to create a new workspace layer in your - Build Directory. + Build Directory. When you create a new workspace layer, it is populated with the README file and the conf directory only. diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index b0c4bfeaa4..424b8cc003 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml @@ -75,7 +75,8 @@ 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 Build Directory + The + Build Directory is created initially when you source the OpenEmbedded build environment setup script (i.e. @@ -212,7 +213,7 @@ When you run this script, your Yocto Project environment is set up, a - Build Directory + Build Directory is created, your working directory becomes the Build Directory, and you are presented with a list of common BitBake targets. Here is an example: @@ -246,7 +247,7 @@ By default, running this script without a - Build Directory + Build Directory argument creates the build directory in your current working directory. If you provide a Build Directory argument when you @@ -330,7 +331,7 @@ The script's parameters are positionally dependent. Consequently, you cannot run the script and provide a - Build Directory + Build Directory name without also providing a port number. In other words, the following syntax is illegal: @@ -386,7 +387,7 @@ By default, running this script without a - Build Directory + Build Directory argument creates a build directory named build. If you provide a Build Directory argument and port number when you @@ -443,7 +444,7 @@ The OpenEmbedded build system creates the - Build Directory + Build Directory when you run one of the build environment setup scripts (i.e. &OE_INIT_FILE; or diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index bd9e517246..da4da8550d 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -536,7 +536,7 @@ The directory within the - Build Directory + Build Directory in which the OpenEmbedded build system places generated objects during a recipe's build process. By default, this directory is the same as the S @@ -734,7 +734,7 @@ variable to "1", "yes", or "true" in your local.conf file, which is located in the - Build Directory: + Build Directory: Here is an example: BB_DANGLINGAPPENDS_WARNONLY = "1" @@ -759,7 +759,7 @@ Disk space monitoring is disabled by default. To enable monitoring, add the BB_DISKMON_DIRS variable to your conf/local.conf file found in the - Build Directory. + Build Directory. Use the following form: BB_DISKMON_DIRS = "action,dir,threshold [...]" @@ -852,7 +852,7 @@ Defines the disk space and free inode warning intervals. To set these intervals, define the variable in your conf/local.conf file in the - Build Directory. + Build Directory. @@ -936,7 +936,7 @@ Set this variable in your local.conf file in the - Build Directory. + Build Directory. @@ -1154,7 +1154,8 @@ Lists the layers to enable during the build. This variable is defined in the bblayers.conf configuration - file in the Build Directory. + file in the + Build Directory. Here is an example: BBLAYERS = " \ @@ -1250,7 +1251,7 @@ BBMULTIFONFIG = "configA configB configC" Each configuration file you use must reside in the - Build Directory's + Build Directory conf/multiconfig directory (e.g. build_directory/conf/multiconfig/configA.conf). @@ -1280,7 +1281,7 @@ PATH variable. If you run BitBake from a directory outside of the - Build Directory, + Build Directory, you must be sure to set BBPATH to point to the Build Directory. @@ -1626,7 +1627,7 @@ Points to the location of the - Build Directory. + Build Directory. You can define this directory indirectly through the &OE_INIT_FILE; and @@ -2595,7 +2596,7 @@ You should only set this variable in the local.conf configuration file found in the - Build Directory. + Build Directory. @@ -2805,7 +2806,8 @@ The destination directory. - The location in the Build Directory + The location in the + Build Directory where components are installed by the do_install task. @@ -3116,7 +3118,7 @@ system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system. By default, this directory resides within the - Build Directory + Build Directory as ${TMPDIR}/deploy. @@ -3189,7 +3191,7 @@ The directory is machine-specific as it contains the ${MACHINE} name. By default, this directory resides within the - Build Directory + Build Directory as ${DEPLOY_DIR}/images/${MACHINE}/. @@ -3794,7 +3796,7 @@ to touch it. By default, the directory is downloads in the - Build Directory. + Build Directory. #DL_DIR ?= "${TOPDIR}/downloads" @@ -4191,7 +4193,7 @@ Typically, you configure this variable in your local.conf file, which is found in the - Build Directory. + Build Directory. Although you can use this variable from within a recipe, best practices dictate that you do not. @@ -4761,7 +4763,7 @@ You define the FILESYSTEM_PERMS_TABLES variable in the conf/local.conf file, which is found in the - Build Directory, to + Build Directory, to point to your custom fs-perms.txt. You can specify more than a single file permissions setting table. The paths you specify to these files must be defined within the @@ -5613,7 +5615,7 @@ Typically, you configure this variable in an image recipe. Although you can use this variable from your local.conf file, which is found in the - Build Directory, + Build Directory, best practices dictate that you do not. To enable extra features from outside the image recipe, @@ -6562,7 +6564,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The combined binary is deposited into the tmp/deploy directory, which is part of the - Build Directory. + Build Directory. @@ -7941,7 +7943,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Specifies the target device for which the image is built. You define MACHINE in the local.conf file found in the - Build Directory. + Build Directory. By default, MACHINE is set to "qemux86", which is an x86-based architecture machine to be emulated using QEMU: @@ -9085,7 +9087,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" This variable, which is set in the local.conf configuration file found in the conf folder of the - Build Directory, + Build Directory, specifies the package manager the OpenEmbedded build system uses when packaging data. @@ -10531,7 +10533,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" build system to attempt before any others by adding something like the following to the local.conf configuration file in the - Build Directory: + Build Directory: PREMIRRORS_prepend = "\ git://.*/.* http://www.yoctoproject.org/sources/ \n \ @@ -11493,7 +11495,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The location in the - Build Directory + Build Directory where unpacked recipe source code resides. By default, this directory is ${WORKDIR}/${BPN}-${PV}, @@ -12411,7 +12413,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" To enable file removal, set the variable to "1" in your conf/local.conf configuration file in your: - Build Directory. + Build Directory. SKIP_FILEDEPS = "1" @@ -14263,7 +14265,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The suffix identifies the libc variant for building. When you are building for multiple variants with the same - Build Directory, + Build Directory, this mechanism ensures that output for different libc variants is kept separate to avoid potential conflicts. @@ -14421,7 +14423,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" ssh. You can set this variable to "1" in your local.conf file in the - Build Directory + Build Directory to have the OpenEmbedded build system automatically run these tests after an image successfully builds: @@ -14789,7 +14791,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" files (other than the shared state cache). By default, the TMPDIR variable points to tmp within the - Build Directory. + Build Directory. @@ -14924,7 +14926,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The top-level - Build Directory. + Build Directory. BitBake automatically sets this variable when you initialize your build environment using either &OE_INIT_FILE; diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 0c949880e7..b2f1048f2e 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml @@ -172,7 +172,7 @@ distribution configuration options, compiler tuning options, general common configuration options, and user configuration options in local.conf, which is found in the - Build Directory. + Build Directory.
@@ -562,7 +562,7 @@ code. However, there is still the question of a task's indirect inputs - the things that were already built and present in the - Build Directory. + Build Directory. The checksum (or signature) for a particular task needs to add the hashes of all the tasks on which the particular task depends. Choosing which dependencies to add is a policy decision. diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index d1ac18fb2f..9fb74172b5 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml @@ -56,7 +56,8 @@ The build_dir argument is optional and specifies the directory the OpenEmbedded build system uses for the build - - the Build Directory. + the + Build Directory. If you do not specify a Build Directory, it defaults to a directory named build in your current working directory. A common practice is to use a different Build Directory for different targets. @@ -142,7 +143,7 @@ Once an image has been built, it often needs to be installed. The images and kernels built by the OpenEmbedded build system are placed in the - Build Directory in + Build Directory in tmp/deploy/images. For information on how to run pre-built images such as qemux86 and qemuarm, see the @@ -978,7 +979,7 @@ Removing TMPDIR (usually tmp/, within the - Build Directory) + Build Directory) can often fix temporary build issues. Removing TMPDIR is usually a relatively cheap operation, because task output will be @@ -1101,7 +1102,7 @@ BUILDHISTORY_COMMIT variable to "1" at the end of your conf/local.conf file found in the - Build Directory: + Build Directory: INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" @@ -1359,7 +1360,7 @@ you can enable writing only image information without any history by adding the following to your conf/local.conf file found in the - Build Directory: + Build Directory: INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "0" @@ -1645,7 +1646,7 @@ sync() calls into the file system on the principle that if there was a significant failure, the - Build Directory + Build Directory contents could easily be rebuilt. diff --git a/documentation/sdk-manual/sdk-appendix-customizing.xml b/documentation/sdk-manual/sdk-appendix-customizing.xml index 965cccc2ca..1317a79ea8 100644 --- a/documentation/sdk-manual/sdk-appendix-customizing.xml +++ b/documentation/sdk-manual/sdk-appendix-customizing.xml @@ -289,7 +289,7 @@ for the SDK alone, create a conf/sdk-extra.conf either in your - Build Directory + Build Directory or within any layer and put your SSTATE_MIRRORS setting within that file. diff --git a/documentation/sdk-manual/sdk-appendix-mars.xml b/documentation/sdk-manual/sdk-appendix-mars.xml index 9957057e99..d960b1009d 100644 --- a/documentation/sdk-manual/sdk-appendix-mars.xml +++ b/documentation/sdk-manual/sdk-appendix-mars.xml @@ -392,7 +392,7 @@ Build System Derived Toolchain: Select this type if you built the toolchain as part of the - Build Directory. + Build Directory. When you select Build system derived toolchain, you are using the toolchain built and @@ -418,7 +418,7 @@ toolchain, the path you provide for the Toolchain Root Location field is the - Build Directory + Build Directory from which you run the bitbake command (e.g /home/scottrif/poky/build). @@ -438,7 +438,7 @@ wiki. If so, the MY_QEMU_ROOTFS directory is found in the - Build Directory + Build Directory and you would browse to and select that directory (e.g. /home/scottrif/build/MY_QEMU_ROOTFS). @@ -487,7 +487,7 @@ Build system derived toolchain, the target kernel you built will be located in the - Build Directory + Build Directory in tmp/deploy/images/machine directory. diff --git a/documentation/sdk-manual/sdk-intro.xml b/documentation/sdk-manual/sdk-intro.xml index 68401690de..47b9bc7ba1 100644 --- a/documentation/sdk-manual/sdk-intro.xml +++ b/documentation/sdk-manual/sdk-intro.xml @@ -215,7 +215,7 @@ built-in devtool functionality. This toolchain is created by running a SDK installer script or through a - Build Directory + Build Directory that is based on your Metadata configuration or extension for your targeted device. The cross-toolchain works with a matching target sysroot. diff --git a/documentation/sdk-manual/sdk-working-projects.xml b/documentation/sdk-manual/sdk-working-projects.xml index 54bc4d739d..526d9208a3 100644 --- a/documentation/sdk-manual/sdk-working-projects.xml +++ b/documentation/sdk-manual/sdk-working-projects.xml @@ -894,7 +894,7 @@ Select this type if you built the toolchain as part of the - Build Directory. + Build Directory. When you select Build system derived toolchain, you are using the toolchain built @@ -925,7 +925,7 @@ the Toolchain Root Location field is the - Build Directory + Build Directory from which you run the bitbake command (e.g /home/scottrif/poky/build). @@ -949,7 +949,7 @@ If so, the MY_QEMU_ROOTFS directory is found in the - Build Directory + Build Directory and you would browse to and select that directory (e.g. /home/scottrif/poky/build/MY_QEMU_ROOTFS). @@ -1003,7 +1003,7 @@ Build system derived toolchain, the target kernel you built will be located in the - Build Directory + Build Directory in tmp/deploy/images/machine directory. diff --git a/documentation/toaster-manual/toaster-manual-reference.xml b/documentation/toaster-manual/toaster-manual-reference.xml index 3a46b61b73..9bd6127f3c 100644 --- a/documentation/toaster-manual/toaster-manual-reference.xml +++ b/documentation/toaster-manual/toaster-manual-reference.xml @@ -879,7 +879,7 @@ When using manage.py commands given a default configuration, you must be sure that your working directory is set to the - Build Directory. + Build Directory. Using manage.py commands from the Build Directory allows Toaster to find the toaster.sqlite file, which is located diff --git a/documentation/toaster-manual/toaster-manual-setup-and-use.xml b/documentation/toaster-manual/toaster-manual-setup-and-use.xml index 966c35d4d3..77291c1eea 100644 --- a/documentation/toaster-manual/toaster-manual-setup-and-use.xml +++ b/documentation/toaster-manual/toaster-manual-setup-and-use.xml @@ -145,7 +145,7 @@ From the directory containing the Toaster database, which by default is the - Build Directory, + Build Directory, invoke the createsuperuser command from manage.py: @@ -378,7 +378,7 @@ This line also runs the checksettings command, which configures the location of the Toaster - Build directory. + Build directory. The Toaster root directory TOASTER_DIR determines where the Toaster build directory is created on the file system. diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 5b64e0f6fe..1d9bd9f2e8 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -528,7 +528,7 @@ $ source &OE_INIT_FILE; Among other things, the script creates the - Build Directory, + Build Directory, which is build in this case and is located in the Source Directory. -- cgit v1.2.3-54-g00ecf