Currently, you can set VIRTUAL-RUNTIME_init_manager to an init system that
isn't in DISTRO_FEATURES. This leads to head scratching over unbootable images.
This adds a sanity check which ensures more valid systems are built.
(From OE-Core rev: c72ec4b52827f75351790eab483d258b2e87611a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This effectively reverts the changes made in b49ddeb11c
to move udev's libexecdir to sbin. The changes caused too many issues in
other places and were not well enough tested this close to a release.
Rather than use base_libdir, the nonarch version is used to try and give some
chance of multilib not being totally broken in the release.
(From OE-Core rev: c50e50fdafad378d75b7b74259a3d55ca0fe3d18)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we put a valid glob like "*/foo/*" into FILES, populate_packages
breaks with a "file exists" message. This is because the glob expansion
does not have "./" prefix however there may already be an entry in
the seen list which does have such a prefix. The easiest/simplest fix
right now is to add the prefix if it doesn't exist which only happens
for certain globs.
(From OE-Core rev: 138c5f3af892e33f576fc7dd268e122b179f82a1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When the mount command is not given the filesystem type to mount, then
it will try all the known filesystems. However, when a filesystem is not
supported by the kernel, the mount function call will return ENODEV.
The following patch, ecd90bc6aa,
introduced a problem because it bailed out on ENODEV too. Instead it should
have only bailed out on ENOMEDIUM.
[YOCTO #4308]
(From OE-Core rev: 82320d2074572477f26887eddc51dc2a1dfea403)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a cross-reference to the section that describes how to
use .bbappend files.
(From yocto-docs rev: 884740c066f0f45cfc85282c6d20737a39d7af88)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section had some problems. It failed to mention the
need to extend FILESPATH by using FILESEXTRAPATHS.
(From yocto-docs rev: e627cf21242a62fb23e93fdae61e8cfce32082a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied some review comments from Paul. Took the warning formatting
out because it sucks.
(From yocto-docs rev: 6c4162777cb686c8b24b15ded2594f4f4a6acba6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some more clarity about how this variable works and the
implications for using the default setting from the base.bbclass
file. Namely, if you are going to have the build system look
for files in your layer and your layer uses an append file,
then you need to also use the FILESEXTRAPATHS variable to
extend FILESPATHS.
(From yocto-docs rev: 2826fa6f9286efb1d5ca6cf85f65266a35bb8cfc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found it confusing due to not specifically accounting for
.bb and .bbappend files. I added some wording to clearly
specify use given the two types of "recipes". Specifically,
if you are going to use a SRC_URI statment from an append
file, the user really should be aware that they will need
to extend the FILESPATH variable by also using FILESEXTRAPATHS
from within that append file.
(From yocto-docs rev: 8fd0047bd5c4598532afc6f0803f6ae23fa213b2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Further down in the section, a second occurrence of ${FILES}
needed changed.
(From yocto-docs rev: 0212a1ebfef4c5a6a0ae76410f7753bbc41d3e82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was inaccurately referencing the ${FILES} directory when
it should be talking about a "files" directory created in the
user's layer where the kernel .bbappend file resides.
(From yocto-docs rev: 2af3a71db6e6d99b9aa4b710e21f3f3bacff0b82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. Fixed broken links to the website downloads page.
2. Added a better link to the oe-init-build-env script.
3. Added a note about the image directory because I discovered
that the QEMU ones have the string "lib32" in prepended
to them.
(From yocto-docs rev: 38074bc97b94a23b115c44aa9f353205914f7cce)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. Made "Metadata" the term instead of "metadata".
2. Created a link to "Metadata" term for first use.
3. Fixed a broken link to the LatencyTop site.
(From yocto-docs rev: 7b53ddd0c9c846c558796d8ae6a46c476ab3b68d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the "Yocto Project" distros and renamed the
openSUSE-project to openSUSE.
(From yocto-docs rev: 8e29abce57d5bfca04633b1b0c5a57809513056f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Discovered a bad typo for the CONFIG_YOCTO_TESTMOD
configuration. I had a "K" in front of it making the
command throw an error. Fixed that.
(From yocto-docs rev: 9c25a69abb12fd2fd472a2b9435a30b2c9ac4f2f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This note is at end of the section on the yocto-bsp and
yocto-kernel tools.
(From yocto-docs rev: 91f33e356412b3d305393483770a4257a872e056)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied "Metadata" for "metadata"
Added a link to the section to help find maintainers.
Some re-wording.
(From yocto-docs rev: 7f40c4dac30d2f54cf09afeb51a5cc83ba0851e9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list was missing several of the linux-yocto kernel types.
(From yocto-docs rev: a91d26ad3a340c54d807458766b7d4f1754df7c2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
