From 193236933b0f4ab91b1625b64e2187e2db4e0e8f Mon Sep 17 00:00:00 2001 From: Brad Bishop Date: Fri, 5 Apr 2019 15:28:33 -0400 Subject: reset upstream subtrees to HEAD Reset the following subtrees on HEAD: poky: 8217b477a1(master) meta-xilinx: 64aa3d35ae(master) meta-openembedded: 0435c9e193(master) meta-raspberrypi: 490a4441ac(master) meta-security: cb6d1c85ee(master) Squashed patches: meta-phosphor: drop systemd 239 patches meta-phosphor: mrw-api: use correct install path Change-Id: I268e2646d9174ad305630c6bbd3fbc1a6105f43d Signed-off-by: Brad Bishop --- poky/documentation/Makefile | 3 +- .../brief-yoctoprojectqs/brief-yoctoprojectqs.xml | 13 +- poky/documentation/bsp-guide/bsp-guide.xml | 4 +- .../dev-manual/dev-manual-common-tasks.xml | 185 +++++++++++++++++- poky/documentation/dev-manual/dev-manual-qemu.xml | 3 + poky/documentation/dev-manual/dev-manual-start.xml | 26 +-- poky/documentation/dev-manual/dev-manual.xml | 4 +- .../documentation/kernel-dev/kernel-dev-common.xml | 36 +++- poky/documentation/kernel-dev/kernel-dev.xml | 4 +- .../mega-manual/figures/bb_multiconfig_files.png | Bin 0 -> 19991 bytes .../mega-manual/figures/bitbake-title.png | Bin 0 -> 5086 bytes poky/documentation/mega-manual/mega-manual.xml | 36 +++- .../overview-manual/overview-manual-concepts.xml | 4 +- .../overview-manual/overview-manual.xml | 7 +- poky/documentation/poky.ent | 38 ++-- .../profile-manual/profile-manual.xml | 4 +- poky/documentation/ref-manual/ref-manual.xml | 4 +- .../ref-manual/ref-system-requirements.xml | 83 +------- poky/documentation/ref-manual/ref-variables.xml | 211 ++++++++++++--------- poky/documentation/ref-manual/resources.xml | 2 +- poky/documentation/sdk-manual/sdk-manual.xml | 4 +- .../toaster-manual/toaster-manual.xml | 4 +- poky/documentation/tools/mega-manual.sed | 60 +++--- 23 files changed, 461 insertions(+), 274 deletions(-) create mode 100644 poky/documentation/mega-manual/figures/bb_multiconfig_files.png create mode 100644 poky/documentation/mega-manual/figures/bitbake-title.png (limited to 'poky/documentation') diff --git a/poky/documentation/Makefile b/poky/documentation/Makefile index 093422f69f..1480e14eac 100644 --- a/poky/documentation/Makefile +++ b/poky/documentation/Makefile @@ -269,7 +269,8 @@ TARFILES = mega-manual.html mega-style.css \ figures/sdk-devtool-add-flow.png figures/sdk-installed-extensible-sdk-directory.png \ figures/sdk-devtool-modify-flow.png figures/sdk-eclipse-dev-flow.png \ figures/sdk-devtool-upgrade-flow.png figures/bitbake-build-flow.png figures/bypqs-title.png \ - figures/overview-manual-title.png figures/sdk-autotools-flow.png figures/sdk-makefile-flow.png + figures/overview-manual-title.png figures/sdk-autotools-flow.png figures/sdk-makefile-flow.png \ + figures/bb_multiconfig_files.png figures/bitbake-title.png endif MANUALS = $(DOC)/$(DOC).html diff --git a/poky/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml b/poky/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml index 5da03a890d..421412ebe4 100644 --- a/poky/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml +++ b/poky/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml @@ -131,7 +131,7 @@ section in the Yocto Project Reference Manual. - $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; libsdl1.2-dev xterm + $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; @@ -148,11 +148,11 @@ $ git clone git://git.yoctoproject.org/poky Cloning into 'poky'... - remote: Counting objects: 428632, done. - remote: Compressing objects: 100% (101203/101203), done. - remote: Total 428632 (delta 320463), reused 428532 (delta 320363) - Receiving objects: 100% (428632/428632), 153.01 MiB | 12.40 MiB/s, done. - Resolving deltas: 100% (320463/320463), done. + remote: Counting objects: 432160, done. + remote: Compressing objects: 100% (102056/102056), done. + remote: Total 432160 (delta 323116), reused 432037 (delta 323000) + Receiving objects: 100% (432160/432160), 153.81 MiB | 8.54 MiB/s, done. + Resolving deltas: 100% (323116/323116), done. Checking connectivity... done. Move to the poky directory and take a look @@ -174,6 +174,7 @@ yocto-2.5.2 yocto-2.6 yocto-2.6.1 + yocto-2.7 yocto_1.5_M5.rc8 For this example, check out the branch based on the diff --git a/poky/documentation/bsp-guide/bsp-guide.xml b/poky/documentation/bsp-guide/bsp-guide.xml index 0d5b6b1365..f559e0809c 100644 --- a/poky/documentation/bsp-guide/bsp-guide.xml +++ b/poky/documentation/bsp-guide/bsp-guide.xml @@ -127,9 +127,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. diff --git a/poky/documentation/dev-manual/dev-manual-common-tasks.xml b/poky/documentation/dev-manual/dev-manual-common-tasks.xml index c75e718d67..893ef7ba07 100644 --- a/poky/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/poky/documentation/dev-manual/dev-manual-common-tasks.xml @@ -5116,15 +5116,15 @@ So, commands such as the following are useful when exploring the data store and running functions: - pydevshell> d.getVar("STAGING_DIR", True) + pydevshell> d.getVar("STAGING_DIR") '/media/build1/poky/build/tmp/sysroots' - pydevshell> d.getVar("STAGING_DIR", False) + pydevshell> d.getVar("STAGING_DIR") '${TMPDIR}/sysroots' pydevshell> d.setVar("FOO", "bar") - pydevshell> d.getVar("FOO", True) + pydevshell> d.getVar("FOO") 'bar' pydevshell> d.delVar("FOO") - pydevshell> d.getVar("FOO", True) + pydevshell> d.getVar("FOO") pydevshell> bb.build.exec_func("do_unpack", d) pydevshell> @@ -6323,9 +6323,180 @@ - +
+ Replicating a Build Offline + + + It can be useful to take a "snapshot" of upstream sources + used in a build and then use that "snapshot" later to + replicate the build offline. + To do so, you need to first prepare and populate your downloads + directory your "snapshot" of files. + Once your downloads directory is ready, you can use it at + any time and from any machine to replicate your build. + + + + Follow these steps to populate your Downloads directory: + + + Create a Clean Downloads Directory: + Start with an empty downloads directory + (DL_DIR). + You start with an empty downloads directory by either + removing the files in the existing directory or by + setting + DL_DIR to point to either an + empty location or one that does not yet exist. + + + Generate Tarballs of the Source Git Repositories: + Edit your local.conf configuration + file as follows: + + DL_DIR = "/home/your-download-dir/" + BB_GENERATE_MIRROR_TARBALLS = "1" + + During the fetch process in the next step, BitBake + gathers the source files and creates tarballs in + the directory pointed to by DL_DIR. + See the + BB_GENERATE_MIRROR_TARBALLS + variable for more information. + + + Populate Your Downloads Directory Without Building: + Use BitBake to fetch your sources but inhibit the + build: + + $ bitbake target --runonly=fetch + + The downloads directory (i.e. + ${DL_DIR}) now has a "snapshot" of + the source files in the form of tarballs, which can + be used for the build. + + + Optionally Remove Any Git or other SCM Subdirectories From the Downloads Directory: + If you want, you can clean up your downloads directory + by removing any Git or other Source Control Management + (SCM) subdirectories such as + ${DL_DIR}/git2/*. + The tarballs already contain these subdirectories. + + + + + + Once your downloads directory has everything it needs regarding + source files, you can create your "own-mirror" and build + your target. + Understand that you can use the files to build the target + offline from any machine and at any time. + + + + Follow these steps to build your target using the files in the + downloads directory: + + + Using Local Files Only: + Inside your local.conf file, add + the + SOURCE_MIRROR_URL + variable, + inherit the own-mirrors + class, and use the + BB_NO_NETWORK + variable to your local.conf. + + SOURCE_MIRROR_URL ?= "file:///home/your-download-dir/" + INHERIT += "own-mirrors" + BB_NO_NETWORK = "1" + + The SOURCE_MIRROR_URL and + own-mirror class set up the system + to use the downloads directory as your "own mirror". + Using the BB_NO_NETWORK + variable makes sure that BitBake's fetching process + in step 3 stays local, which means files from + your "own-mirror" are used. + + + Start With a Clean Build: + You can start with a clean build by removing the + ${TMPDIR} + directory or using a new + Build Directory. + + + Build Your Target: + Use BitBake to build your target: + + $ bitbake target + + The build completes using the known local "snapshot" of + source files from your mirror. + The resulting tarballs for your "snapshot" of source + files are in the downloads directory. + + The offline build does not work if recipes + attempt to find the latest version of software + by setting + SRCREV + to + ${AUTOREV}: + + SRCREV = "${AUTOREV}" + + When a recipe sets + SRCREV to + ${AUTOREV}, the build system + accesses the network in an attempt to determine the + latest version of software from the SCM. + Typically, recipes that use + AUTOREV are custom or + modified recipes. + Recipes that reside in public repositories + usually do not use AUTOREV. + + If you do have recipes that use + AUTOREV, you can take steps to + still use the recipes in an offline build. + Do the following: + + + Use a configuration generated by + enabling + build history. + + + Use the + buildhistory-collect-srcrevs + command to collect the stored + SRCREV values from + the build's history. + For more information on collecting these + values, see the + "Build History Package Information" + section. + + + Once you have the correct source + revisions, you can modify those recipes + to to set SRCREV + to specific versions of the software. + + + + + + + +
+
Speeding Up a Build @@ -6892,8 +7063,8 @@ MACHINE = "qemux86-64" DEFAULTTUNE = "x86-64-x32" - baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE', True) \ - or 'INVALID'), True) or 'lib'}" + baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE') \ + or 'INVALID')) or 'lib'}" Once you have set up your configuration file, use BitBake to build an image that supports the x32 psABI. diff --git a/poky/documentation/dev-manual/dev-manual-qemu.xml b/poky/documentation/dev-manual/dev-manual-qemu.xml index 4e7b5de4e8..f5a0d64afe 100644 --- a/poky/documentation/dev-manual/dev-manual-qemu.xml +++ b/poky/documentation/dev-manual/dev-manual-qemu.xml @@ -590,6 +590,9 @@ nographic: Disables the video console, which sets the console to "ttys0". + This option is useful when you have logged into a server + and you do not want to disable forwarding from the + X Window System (X11) to your workstation or laptop. serial: diff --git a/poky/documentation/dev-manual/dev-manual-start.xml b/poky/documentation/dev-manual/dev-manual-start.xml index d37c0303f3..6ec5c3cf43 100644 --- a/poky/documentation/dev-manual/dev-manual-start.xml +++ b/poky/documentation/dev-manual/dev-manual-start.xml @@ -44,7 +44,7 @@ Determine Who is Going to be Developing: You need to understand who is going to be doing anything - related to the Yocto Project and what their roles would be. + related to the Yocto Project and determine their roles. Making this determination is essential to completing steps two and three, which are to get your equipment together and set up your development environment's hardware topology. @@ -951,11 +951,11 @@ $ git clone git://git.yoctoproject.org/poky Cloning into 'poky'... - remote: Counting objects: 416542, done. - remote: Compressing objects: 100% (98611/98611), done. - remote: Total 416542 (delta 311104), reused 416377 (delta 310939) - Receiving objects: 100% (416542/416542), 150.39 MiB | 15.77 MiB/s, done. - Resolving deltas: 100% (311104/311104), done. + remote: Counting objects: 432160, done. + remote: Compressing objects: 100% (102056/102056), done. + remote: Total 432160 (delta 323116), reused 432037 (delta 323000) + Receiving objects: 100% (432160/432160), 153.81 MiB | 8.54 MiB/s, done. + Resolving deltas: 100% (323116/323116), done. Checking connectivity... done. Unless you specify a specific development branch or @@ -1037,13 +1037,15 @@ . . . - remotes/origin/master-next - remotes/origin/master-next2 - remotes/origin/morty - remotes/origin/pinky - remotes/origin/purple remotes/origin/pyro + remotes/origin/pyro-next remotes/origin/rocko + remotes/origin/rocko-next + remotes/origin/sumo + remotes/origin/sumo-next + remotes/origin/thud + remotes/origin/thud-next + remotes/origin/warrior @@ -1125,8 +1127,10 @@ yocto-2.5 yocto-2.5.1 yocto-2.5.2 + yocto-2.5.3 yocto-2.6 yocto-2.6.1 + yocto-2.7 yocto_1.5_M5.rc8 diff --git a/poky/documentation/dev-manual/dev-manual.xml b/poky/documentation/dev-manual/dev-manual.xml index b54c0d65d5..5dda016d78 100644 --- a/poky/documentation/dev-manual/dev-manual.xml +++ b/poky/documentation/dev-manual/dev-manual.xml @@ -112,9 +112,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. diff --git a/poky/documentation/kernel-dev/kernel-dev-common.xml b/poky/documentation/kernel-dev/kernel-dev-common.xml index 9052876122..7ff4cba3b0 100644 --- a/poky/documentation/kernel-dev/kernel-dev-common.xml +++ b/poky/documentation/kernel-dev/kernel-dev-common.xml @@ -1479,15 +1479,33 @@ To use the menuconfig tool in the Yocto - Project development environment, you must launch it using - BitBake. - Thus, the environment must be set up using the - &OE_INIT_FILE; - script found in the - Build Directory. - You must also be sure of the state of your build's - configuration in the - Source Directory. + Project development environment, you must do the following: + + + Because you launch menuconfig + using BitBake, you must be sure to set up your + environment by running the + &OE_INIT_FILE; + script found in the + Build Directory. + + + You must be sure of the state of your build's + configuration in the + Source Directory. + + + Your build host must have the following two packages + installed: + + libncurses5-dev + libtinfo-dev + + + + + + The following commands initialize the BitBake environment, run the do_kernel_configme diff --git a/poky/documentation/kernel-dev/kernel-dev.xml b/poky/documentation/kernel-dev/kernel-dev.xml index fc46c205b5..33553df060 100644 --- a/poky/documentation/kernel-dev/kernel-dev.xml +++ b/poky/documentation/kernel-dev/kernel-dev.xml @@ -97,9 +97,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. diff --git a/poky/documentation/mega-manual/figures/bb_multiconfig_files.png b/poky/documentation/mega-manual/figures/bb_multiconfig_files.png new file mode 100644 index 0000000000..041f06403b Binary files /dev/null and b/poky/documentation/mega-manual/figures/bb_multiconfig_files.png differ diff --git a/poky/documentation/mega-manual/figures/bitbake-title.png b/poky/documentation/mega-manual/figures/bitbake-title.png new file mode 100644 index 0000000000..cb290154da Binary files /dev/null and b/poky/documentation/mega-manual/figures/bitbake-title.png differ diff --git a/poky/documentation/mega-manual/mega-manual.xml b/poky/documentation/mega-manual/mega-manual.xml index 7a4199198b..2c518f9511 100644 --- a/poky/documentation/mega-manual/mega-manual.xml +++ b/poky/documentation/mega-manual/mega-manual.xml @@ -12,9 +12,11 @@ The Yocto Project Mega-Manual is a concatenation of the published - Yocto Project HTML manuals for the given release. - The manual exists to help users efficiently search for strings - across the entire Yocto Project documentation set. + Yocto Project HTML manuals along with the corresponding BitBake + User Manual for the given release. + The Mega-Manual exists to help users efficiently search for strings + across the entire Yocto Project documentation set inclusive of + the BitBake User Manual. @@ -81,9 +83,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. @@ -322,6 +324,30 @@ + + + + + + + + + + + + + + + + + + + While the Yocto Project Team attempts to ensure all Yocto Project releases are one hundred percent compatible with each officially @@ -199,26 +192,12 @@ Here is some old list items to show the form: $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; - Graphical and Eclipse Plug-In Extras: - Packages recommended if the host system has graphics - support or if you are going to use the Eclipse - IDE: - - $ sudo apt-get install libsdl1.2-dev xterm - Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo apt-get install make xsltproc docbook-utils fop dblatex xmlto - OpenEmbedded Self-Test (oe-selftest): - Packages needed if you are going to run - oe-selftest: - - $ sudo apt-get install python-git - -
@@ -236,27 +215,13 @@ Here is some old list items to show the form: $ sudo dnf install &FEDORA_HOST_PACKAGES_ESSENTIAL; - Graphical and Eclipse Plug-In Extras: - Packages recommended if the host system has graphics - support or if you are going to use the Eclipse - IDE: - - $ sudo dnf install SDL-devel xterm - Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: - $ sudo dnf install make docbook-style-dsssl docbook-style-xsl \ + $ sudo dnf install docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt dblatex xmlto - OpenEmbedded Self-Test (oe-selftest): - Packages needed if you are going to run - oe-selftest: - - $ sudo dnf install python3-GitPython - - @@ -274,33 +239,13 @@ Here is some old list items to show the form: $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL; - Graphical and Eclipse Plug-In Extras: - Packages recommended if the host system has graphics - support or if you are going to use the Eclipse - IDE: - - $ sudo zypper install libSDL-devel xterm - Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: - $ sudo zypper install make dblatex xmlto - - OpenEmbedded Self-Test (oe-selftest): - Packages needed if you are going to run - oe-selftest: - - $ sudo zypper install python-GitPython + $ sudo zypper install dblatex xmlto - - Sanity testing, through the - testimage - classes, does not work on systems using the - Wicked - network manager. - @@ -315,7 +260,7 @@ Here is some old list items to show the form: Packages needed to build an image for a headless system: - $ sudo yum install &CENTOS_HOST_PACKAGES_ESSENTIAL; SDL-devel xterm + $ sudo yum install &CENTOS_HOST_PACKAGES_ESSENTIAL; Notes @@ -337,27 +282,13 @@ Here is some old list items to show the form: - Graphical and Eclipse Plug-In Extras: - Packages recommended if the host system has graphics - support or if you are going to use the Eclipse - IDE: - - $ sudo yum install SDL-devel xterm - Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: - $ sudo yum install make docbook-style-dsssl docbook-style-xsl \ + $ sudo yum install docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt dblatex xmlto - OpenEmbedded Self-Test (oe-selftest): - Packages needed if you are going to run - oe-selftest: - - $ sudo yum install GitPython - - diff --git a/poky/documentation/ref-manual/ref-variables.xml b/poky/documentation/ref-manual/ref-variables.xml index 9f6bc1adad..6470c739c2 100644 --- a/poky/documentation/ref-manual/ref-variables.xml +++ b/poky/documentation/ref-manual/ref-variables.xml @@ -3621,60 +3621,6 @@ - DISK_SIGNATURE - - DISK_SIGNATURE[doc] = "A 32-bit MBR disk signature used by directdisk images." - - - - - A 32-bit MBR disk signature used by - directdisk images. - - - - By default, the signature is set to an automatically - generated random value that allows the OpenEmbedded - build system to create a boot loader. - You can override the signature in the image recipe - by setting DISK_SIGNATURE to an - 8-digit hex string. - You might want to override - DISK_SIGNATURE if you want the disk - signature to remain constant between image builds. - - - - When using Linux 3.8 or later, you can use - DISK_SIGNATURE to specify the root - by UUID to allow the kernel to locate the root device - even if the device name changes due to differences in - hardware configuration. - By default, ROOT_VM is set - as follows: - - ROOT_VM ?= "root=/dev/sda2" - - However, you can change this to locate the root device - using the disk signature instead: - - ROOT_VM = "root=PARTUUID=${DISK_SIGNATURE}-02" - - - - - As previously mentioned, it is possible to set the - DISK_SIGNATURE variable in your - local.conf file to a fixed - value if you do not want syslinux.cfg - changing for each build. - You might find this useful when you want to upgrade the - root filesystem on a device without having to recreate or - modify the master boot record. - - - - DISTRO DISTRO[doc] = "The short name of the distribution. If the variable is blank, meta/conf/distro/defaultsetup.conf will be used." @@ -3877,7 +3823,7 @@ DISTRO_FEATURES_DEFAULT from a custom distro configuration file: - DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC} myfeature" + DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} myfeature" @@ -3924,13 +3870,14 @@ + + A convenience variable that specifies the list of distro features that are specific to the C library (libc). @@ -3940,6 +3887,7 @@ +--> DISTRO_FEATURES_NATIVE @@ -5012,9 +4960,17 @@ A subset of OVERRIDES used by the OpenEmbedded build system for creating FILESPATH. - You can find more information on how overrides are handled - in the - BitBake User Manual. + The FILESOVERRIDES variable uses + overrides to automatically extend the + FILESPATH + variable. + For an example of how that works, see the + FILESPATH + variable description. + Additionally, you find more information on how overrides + are handled in the + "Conditional Syntax (Overrides)" + section of the BitBake User Manual. @@ -5041,11 +4997,14 @@ - The default set of directories the OpenEmbedded build system - uses when searching for patches and files. - During the build process, BitBake searches each directory in - FILESPATH in the specified order when - looking for files and patches specified by each + The default set of directories the OpenEmbedded build + system uses when searching for patches and files. + + + + During the build process, BitBake searches each directory + in FILESPATH in the specified order + when looking for files and patches specified by each file:// URI in a recipe's SRC_URI statements. @@ -5060,23 +5019,62 @@ FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", \ "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}" - - Do not hand-edit the FILESPATH - variable. - If you want the build system to look in directories - other than the defaults, extend the - FILESPATH variable by using the - FILESEXTRAPATHS - variable. + The FILESPATH variable is automatically + extended using the overrides from the + FILESOVERRIDES + variable. + Notes + + + Do not hand-edit the + FILESPATH variable. + If you want the build system to look in + directories other than the defaults, extend the + FILESPATH variable by + using the + FILESEXTRAPATHS + variable. + + + Be aware that the default + FILESPATH directories do + not map to directories in custom layers + where append files + (.bbappend) are used. + If you want the build system to find patches + or files that reside with your append files, + you need to extend the + FILESPATH variable by + using the FILESEXTRAPATHS + variable. + + - Be aware that the default FILESPATH - directories do not map to directories in custom layers - where append files (.bbappend) - are used. - If you want the build system to find patches or files - that reside with your append files, you need to extend - the FILESPATH variable by using - the FILESEXTRAPATHS variable. + + + + You can take advantage of this searching behavior in + useful ways. + For example, consider a case where the following + directory structure exists for general and machine-specific + configurations: + + files/defconfig + files/MACHINEA/defconfig + files/MACHINEB/defconfig + + Also in the example, the SRC_URI + statement contains "file://defconfig". + Given this scenario, you can set + MACHINE + to "MACHINEA" and cause the build system to use files + from files/MACHINEA. + Set MACHINE to "MACHINEB" and the + build system uses files from + files/MACHINEB. + Finally, for any machine other than "MACHINEA" and + "MACHINEB", the build system uses files from + files/defconfig. @@ -6076,11 +6074,12 @@ Notes - If you add "live" to - IMAGE_FSTYPES inside an image - recipe, be sure that you do so prior to the - "inherit image" line of the recipe or the live - image will not build. + If an image recipe uses the "inherit image" line + and you are setting + IMAGE_FSTYPES inside the + recipe, you must set + IMAGE_FSTYPES prior to + using the "inherit image" line. Due to the way the OpenEmbedded build system @@ -6866,6 +6865,44 @@ + INHIBIT_SYSROOT_STRIP + + INHIBIT_SYSROOT_STRIP[doc] = "If set to "1", causes the build to not strip binaries in the resulting sysroot." + + + + + If set to "1", causes the build to not strip binaries in + the resulting sysroot. + + + + By default, the OpenEmbedded build system strips + binaries in the resulting sysroot. + When you specifically set the + INHIBIT_SYSROOT_STRIP variable to + "1" in your recipe, you inhibit this stripping. + + + + If you want to use this variable, include the + staging + class. + This class uses a sys_strip() + function to test for the variable and acts accordingly. + + Use of the INHIBIT_SYSROOT_STRIP + variable occurs in rare and special circumstances. + For example, suppose you are building bare-metal + firmware by using an external GCC toolchain. + Furthermore, even if the toolchain's binaries are + strippable, other files exist that are needed for the + build that are not strippable. + + + + + INITRAMFS_FSTYPES INITRAMFS_FSTYPES[doc] = "Defines the format for the output image of an initial RAM filesystem (initramfs), which is used during boot." @@ -9933,7 +9970,6 @@ /bin/.debug. Source files are placed in /usr/src/debug. - This is the default behavior. "debug-file-directory": Debug symbol files are @@ -9957,6 +9993,7 @@ ".debug" previously described with the exception that all source files are placed in a separate *-src pkg. + This is the default behavior. @@ -13002,7 +13039,7 @@ /meta-poky/conf/distro/poky.conf) defines the SDK_VERSION as follows: - SDK_VERSION := "${@'${DISTRO_VERSION}'.replace('snapshot-${DATE}','snapshot')}" + SDK_VERSION = "${@d.getVar('DISTRO_VERSION').replace('snapshot-${DATE}','snapshot')}" diff --git a/poky/documentation/ref-manual/resources.xml b/poky/documentation/ref-manual/resources.xml index be0469616c..6a0cee8a56 100644 --- a/poky/documentation/ref-manual/resources.xml +++ b/poky/documentation/ref-manual/resources.xml @@ -155,7 +155,7 @@ - BitBake User Manual: + BitBake User Manual: A comprehensive guide to the BitBake tool. If you want information on BitBake, see this manual. diff --git a/poky/documentation/sdk-manual/sdk-manual.xml b/poky/documentation/sdk-manual/sdk-manual.xml index 7f93d5f611..1828119dfc 100644 --- a/poky/documentation/sdk-manual/sdk-manual.xml +++ b/poky/documentation/sdk-manual/sdk-manual.xml @@ -62,9 +62,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. diff --git a/poky/documentation/toaster-manual/toaster-manual.xml b/poky/documentation/toaster-manual/toaster-manual.xml index dcc2990dcd..42dc6a33eb 100644 --- a/poky/documentation/toaster-manual/toaster-manual.xml +++ b/poky/documentation/toaster-manual/toaster-manual.xml @@ -72,9 +72,9 @@ Released with the Yocto Project 2.6 Release. - 2.6.1 + 2.7 &REL_MONTH_YEAR; - Released with the Yocto Project 2.6.1 Release. + Released with the Yocto Project 2.7 Release. diff --git a/poky/documentation/tools/mega-manual.sed b/poky/documentation/tools/mega-manual.sed index f6e205feb3..79bbeef575 100644 --- a/poky/documentation/tools/mega-manual.sed +++ b/poky/documentation/tools/mega-manual.sed @@ -1,40 +1,36 @@ -# Processes poky-ref-manual and yocto-project-qs manual (-- style). -# This style is for manual folders like "yocto-project-qs" and "poky-ref-manual". -# This is the old way that did it. Can't do that now that we have "bitbake-user-manual" strings -# in the mega-manual. -# s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/[a-z]*-[a-z]*-[a-z]*/[a-z]*-[a-z]*-[a-z]*.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/yocto-project-qs/yocto-project-qs.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/poky-ref-manual/poky-ref-manual.html#@"link" href="#@g +# Processes bitbake-user-manual (-- style). +# This style is for manual three-word folders, which currently is only the BitBake User Manual. +# We used to have the "yocto-project-qs" and "poky-ref-manual" folders but no longer do. +# s@"ulink" href="http://www.yoctoproject.org/docs/2.7/[a-z]*-[a-z]*-[a-z]*/[a-z]*-[a-z]*-[a-z]*.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/bitbake-user-manual/bitbake-user-manual.html#@"link" href="#@g -# Processes all other manuals (- style) except for the BitBake User Manual because -# it is not included in the mega-manual. +# Processes all other manuals (- style). # This style is for manual folders that use two word, which is the standard now (e.g. "ref-manual"). -# This was the one-liner that worked before we introduced the BitBake User Manual, which is -# not in the mega-manual. -# s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/[a-z]*-[a-z]*/[a-z]*-[a-z]*.html#@"link" href="#@g +# Here is the one-liner: +# s@"ulink" href="http://www.yoctoproject.org/docs/2.7/[a-z]*-[a-z]*/[a-z]*-[a-z]*.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/sdk-manual/sdk-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/bsp-guide/bsp-guide.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/dev-manual/dev-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/overview-manual/overview-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/kernel-dev/kernel-dev.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/profile-manual/profile-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/ref-manual/ref-manual.html#@"link" href="#@g -s@"ulink" href="http://www.yoctoproject.org/docs/2.6.1/toaster-manual/toaster-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/sdk-manual/sdk-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/bsp-guide/bsp-guide.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/overview-manual/overview-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/brief-yoctoprojectqs/brief-yoctoprojectqs.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/kernel-dev/kernel-dev.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/profile-manual/profile-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#@"link" href="#@g +s@"ulink" href="http://www.yoctoproject.org/docs/2.7/toaster-manual/toaster-manual.html#@"link" href="#@g # Process cases where just an external manual is referenced without an id anchor -s@Yocto Project Quick Build@Yocto Project Quick Build@g -s@Yocto Project Quick Start@Yocto Project Quick Start@g -s@Yocto Project Development Tasks Manual@Yocto Project Development Tasks Manual@g -s@Yocto Project Overview and Concepts Manual@Yocto project Overview and Concepts Manual@g -s@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@g -s@Yocto Project Board Support Package (BSP) Developer's Guide@Yocto Project Board Support Package (BSP) Developer's Guide@g -s@Yocto Project Profiling and Tracing Manual@Yocto Project Profiling and Tracing Manual@g -s@Yocto Project Linux Kernel Development Manual@Yocto Project Linux Kernel Development Manual@g -s@Yocto Project Reference Manual@Yocto Project Reference Manual@g -s@Toaster User Manual@Toaster User Manual@g +s@Yocto Project Quick Build@Yocto Project Quick Build@g +s@BitBake User Manual@BitBake User Manual@g +s@Yocto Project Development Tasks Manual@Yocto Project Development Tasks Manual@g +s@Yocto Project Overview and Concepts Manual@Yocto project Overview and Concepts Manual@g +s@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@Yocto Project Application Development and the Extensible Software Development Kit (eSDK)@g +s@Yocto Project Board Support Package (BSP) Developer's Guide@Yocto Project Board Support Package (BSP) Developer's Guide@g +s@Yocto Project Profiling and Tracing Manual@Yocto Project Profiling and Tracing Manual@g +s@Yocto Project Linux Kernel Development Manual@Yocto Project Linux Kernel Development Manual@g +s@Yocto Project Reference Manual@Yocto Project Reference Manual@g +s@Toaster User Manual@Toaster User Manual@g # Process a single, rouge occurrence of a linked reference to the Mega-Manual. -s@Yocto Project Mega-Manual@Yocto Project Mega-Manual@g +s@Yocto Project Mega-Manual@Yocto Project Mega-Manual@g -- cgit v1.2.3