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/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 +- 4 files changed, 134 insertions(+), 166 deletions(-) (limited to 'poky/documentation/ref-manual') diff --git a/poky/documentation/ref-manual/ref-manual.xml b/poky/documentation/ref-manual/ref-manual.xml index f834d2dea..26295f02f 100644 --- a/poky/documentation/ref-manual/ref-manual.xml +++ b/poky/documentation/ref-manual/ref-manual.xml @@ -128,9 +128,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/ref-manual/ref-system-requirements.xml b/poky/documentation/ref-manual/ref-system-requirements.xml index 0db84e31f..5f2b9f6ce 100644 --- a/poky/documentation/ref-manual/ref-system-requirements.xml +++ b/poky/documentation/ref-manual/ref-system-requirements.xml @@ -97,18 +97,9 @@ OpenSUSE 42.3 - + 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 9f6bc1ada..6470c739c 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 be0469616..6a0cee8a5 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. -- cgit v1.2.1