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 --- .../dev-manual/dev-manual-common-tasks.xml | 59 ++++++++++++---------- 1 file changed, 31 insertions(+), 28 deletions(-) (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml') 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" -- cgit v1.2.3-54-g00ecf