Clearly I didn't test this part of the code - lists don't have an "add"
method. Needless to say I have tested it now.
(From OE-Core rev: 063ed9058a14775f77e7875d4f6ef5719fa03f18)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A sensible assumption is that BSPs have a USB keyboard and mouse connected
unless told otherwise, so flip the logic in the formfactor config script that
previously assumed that a keyboard was not connected by default.
[ YOCTO #9174 ]
(From OE-Core rev: a82ce3e477a475dccea3837eabacd9e93b873ee6)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ls adds a '.' at the end of the permission field list on SELinux
machines, filter this out so root tests work on SELinux machines.
And backport one patch for other tests.
(From OE-Core rev: 2981d026460658fd2db7df3618d718fe6e8bfca0)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libitm is already disabled for big endian MIPS, but needs to be
disabled for little endian MIPS targets too.
(From OE-Core rev: 421e8ac60ff6eb87e66ebeab6f14d74216386578)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a build-sdk command which is only available within the extensible
SDK that builds a derivative extensible SDK. The idea is recipes in the
workspace become a part of the new SDK - for example, this allows taking
a vendor provided SDK, adding a few libs and then producing a new SDK
with those included.
When normally building the extensible SDK, the workspace is excluded;
here we need to copy into the new SDK (renaming it in the process); the
recipes' task signatures become locked and thus the sources are no
longer needed, so they are removed along with the workspace bbappends
which would interfere with the locked signatures. Additionally we need
to just copy the configuration files (i.e. local.conf and auto.conf)
rather than filtering and appending to them since that work has already
been done when constructing the original SDK. The extra sstate artifacts
from workspace recipes are also determined and copied into the new SDK
in minimal mode (on the assumption that you won't set up a new sstate
mirror).
This reuses some code from build-image, so that needed to be
generalised to allow that.
Implements [YOCTO #8892].
(From OE-Core rev: 59e207ff6dd4b50a8905e14bc9292cf2794f4e7a)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hyphens aren't allowed in python identifiers, so you shouldn't use them
in module names or they are more difficult to import.
(From OE-Core rev: e8f6db9436dfc923e236f2cbc08f357e3b24fd5d)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixing one of the recipes not to contain unsafe references to paths
results in this QA test failing. Improve the test so that we test
the recipe works, then if we intentionally break the recipe, the
issue is detected.
Also split out the binaries test from the scripts test. The binaries
issue may also get 'fixed' in future and need the same fix.
(From OE-Core rev: 68db200ca5b404d6c0aa0cbf5a587397d0aa65da)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previously, the checking for unsafe references is not strict enough. It
only checks whether '/usr/' is in the script. As a result, any script
containing statements like below will match this check.
PATH="/bin:/sbin:/usr/bin:/usr/sbin"
However, as we can see, this is actually not an unsafe reference. What
we really want to check is something like '/usr/bin/tail', so we should
make the checking stricter.
This patch solves the QA warning in gzip and nfs-utils.
(From OE-Core rev: f818f7359c1a5db2c5c041c42eecb9f0434d9800)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Building Images" section, we just plow into the command
line experience without giving any indication of a GUI option
through which to try out the Yocto Project. I updated the
paragraph introducing the build stuff by presenting the command
line method or a GUI method via Toaster.
(From yocto-docs rev: c7d0b2e1c3f9746bdcf2ba8ded71ee14cfa17e58)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied better wording to a couple areas in this section as
pointed out by the review.
Fixes [YOCTO #9114]
(From yocto-docs rev: f5a402aa08b102c767e112d8df05041650733d54)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
Added a couple more clarifications for some nativesdk term
uses. Minor edits to help make things clearer.
(From yocto-docs rev: 38082e1120861332674f97f67966b1f5cec7dc03)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created the new section for the devtool upgrade flow.
(From yocto-docs rev: f3a7f78305ce5045604d9892e18b31b7eabcba62)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a new figure for the devtool upgrade flow. Put the figure
in the "figures" folder of the dev-manual and the mega-manual.
Updated the Makefile to include the new figure when creating
Tarball of the dev-manual and the mega-manual.
(From yocto-docs rev: 4b504f6f179ca7c7e9a69f23fc25b1f33ced8e44)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made some review changes to the workflow structure, devtool
add flow, and devtool modify flow diagrams.
(From yocto-docs rev: f432d9b0270615974e67a0cc243560fdbfa44724)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Closing in on the devtool add and devtool modify sections.
(From yocto-docs rev: 202b688c03cc1801576bbed3b771bb329f6b8520)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New figure and some writer notes for now
(From yocto-docs rev: 0a627626f5f353e514b0225b468b0bd0fa3ceef3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
dev-manual: I did not have the checksum figure there or the sources
directory.
mega-manual: Per normal, had to copy the updated figure into the
figures directory of the mega-manual.
(From yocto-docs rev: d6fb3373b2f3c1e89da87d3e8b9877e643f73c8e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This style is for review purposes and can be implemented in
the XML file using <para role='writernotes'>. The text in the
paragraph is rendered red.
(From yocto-docs rev: db990802594af3a70b11e320c06fe6a9dc80579b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a new figure for devtool add flow. Added support
for it in the Makefile. The figure, as usual, needs to
reside in the figures directory in both the dev-manual and
the mega-manual.
(From yocto-docs rev: 2040a31b806fdade060f7a4182a09673b76db7b3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9114]
Added a "Notes" box to address run script naming points
and the fact that running a task's script is identical to
what BitBake would do when it runs the task.
(From yocto-docs rev: ddfba59743c977a3a3483ed9053434d3c622f698)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
I applied some review comments for the changes made to several
areas in both these manuals. Minor wording fixes and the
dropping of some changes as directed by Joshua Lock.
(From yocto-docs rev: 71af89da612c37162ba27844c297879d643caf65)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9114]
Added more detail on how to run commands from within the devshell.
(From yocto-docs rev: 6535a8b80bbad3a4ece191c7e5a145ef5e09f1e2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The manage.py createsuperuser command must be run from the directory
containing the Toaster database, and not from the root of the checkout
directory, as the manual indicated. Amend the section to provide the
correct instructions.
(From yocto-docs rev: 41fa8a04c947169d971c5e1ecb4619249d1dc7b3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
I went through and made some judgement calls on the use of
"native" and "sdknative". I tried to make sure that the reader
understood the real meaning of these terms.
(From yocto-docs rev: d711e8c6dfb32a4ad79e9d11dbf44fbc759d0245)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two instances existed instructing the user about a prompt
for the json file prompt. These have been removed.
(From yocto-docs rev: f45cb8c5db70ef15e685c68508fd3941d8c6727e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8542]
I updated the description with a new example specific to Git.
When you use Git, you have to specifically set the S directory
for things to work.
(From yocto-docs rev: 10d71ccda461098fd8c94677d91fd261f6edf508)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8634]
To clear up the behavior the COPY_LIC_DIRS, COPY_LIC_MANIFEST,
and LICENSE_CREATE_PACKAGE variable behaviors, I updated the
glossary descriptions of the variables. Also, added more info
to the "Providing License Text" section in the dev-manual. Tied
everything together with good referencing.
(From yocto-docs rev: e7b2a1ed29dcd9d572b71f756e7705e6499a05ac)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I included a new paragraph at the end of the section describing
configuration in the "Closer Look" chapter. Cases exist when
two configuration files set the same variable. Depending on the
order, the last configuration file parsed is the one that actually
sets the variable.
Fixes [YOCTO #8914]
(From yocto-docs rev: 260e7dea7879846bcd3f3475cef001e512c657f0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8634]
I updated the "Providing License Text" section to include some
verbiage on the new CREATE_LICENSE_PACKAGE variable.
(From yocto-docs rev: db2155875dd741000e5f67253486580bba70584f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8542]
I did a bit of re-wording based on the suggested stuff in the
bug.
(From yocto-docs rev: 8ab2ae205f79429c2986a9ba86bcba07f5e05cd8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9147]
Added the d.expand(expression) fuction to the list of functions
in the "Accessing Datastore Variables Using Python" section.
(Bitbake rev: 19507b80f35d37dc4b1614bd390b8e261dd4a2bd)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9148]
Added a note about Variable expressions (e.g. ${X}) are no longer
expanded within Python functions.
(Bitbake rev: 4ebe55cb8c8db1c5cf5d127e213487c5a453a68a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8567]
Updated the variable list describing the variables that affect
how environment variables are handled. Also updated the section
on how those variables are passed.
(Bitbake rev: 91cb52b1e77bba9d046239933b5c0513d01e6824)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton
Ross Burton
He Zhe
Andre McCurdy
Richard Purdie
Chen Qi
Scott Rifenbark
Belen Barros Pena
Belen Barros Pena