Removed the bitbake option and the TMPDIR terminology.
(From yocto-docs rev: c543e00eeb9e9a8074dfb195c971c37c095ecbdd)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The term "meta-toolchain" is legacy now. I went through and removed
its use except for where it appears still as output from the
oe-init-build-env script.
(From yocto-docs rev: 1cc134060459278997d57f1293f54091c5404d85)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the heading for "Optionally Building a Toolchain
Installer" to "Building an SDK Installer". This changes the
heading and many references to that heading.
(From yocto-docs rev: 97d8cd34d0dd0993b1b1135bb75f2212bb46878a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Better placement of this link. It did not need to be in the
<literallayout> example.
(From yocto-docs rev: 53c33ea4cc929e016812f0d3aac0d302758dc0f8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Removed some eMenlow stuff
* Cleaned up the description of the BSP structures we have now.
* Various links fixed into the SDK manual.
* Other minor fixes.
(From yocto-docs rev: 5e45005d7ff2254df2754a5ea2d7efd7f1c19a42)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Probably should have committed these separately but....
* Updated the BSP guide to use an example that we support.
I removed the eMenlow stuff completely.
* Fixed poky.ent so the 15.0.0 stuff is used for the variables.
This supports the 2.1 release.
(From yocto-docs rev: 598b261725235b6f160561db22bd9f31ec721066)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fixed some wordings
* Fixed some links for consistency
(From yocto-docs rev: 9737ba3a572140bec892ffb555241a2259bd517a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Set year to 2016 and fixed some variables.
(From yocto-docs rev: d1e15dac45cb689c59d9301af776101336e07bf2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a devtool add and devtool modify flow digram. Updated
the Makefile to support those figures in the tarball creation.
(From yocto-docs rev: b40692065262dee0209329886b6e3a743c32b1bd)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I am using "red" text to indicate sections of the manual that
are my development notes.
(From yocto-docs rev: 95b432d852ac3248874a2a958d4a80e59187f062)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I left off the file extension when I added a new figure to the
SDK manual. This caused the tarball to fail.
(From yocto-docs rev: f1984b00b44ad7f1890adecdb7e2f6dd4af5b96c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows you to use the following to make a paragraph display
using red-colored text:
<para role='writernotes'>Here is the sentence.</para>
What this allows is to create areas in the manual that are
easily identified as questions to the reviewers.
(From yocto-docs rev: 007ea508a36f453c66970666490a82885a8749e1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added text and a new figure to show the resulting directory
structure from running the SDK installation .sh script.
(From yocto-docs rev: 3c5aec4a0088262e60ee6becb5e34552feeb6151)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The xslproc needs special handling of the statement that applies
the numbering for appendices. I updated the line to use that
format so when making the file you do not get a billion
unrecognized parameter errors.
(From yocto-docs rev: a2787b7a6d045196c0d524e11531ca3aca41b9c2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Including three figs for Toaster manual.
(From yocto-docs rev: c41f9859b6cfc4e34b8e0d0e812fad0b8dd44540)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I applied some grammar and writing edits to a large patch of new
text.
(From yocto-docs rev: 67cd700131e7cbca5769f25328772406f860d519)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These figures were added through a patch and needed to also
be local to the figures directory in the mega-manual.
Also, the Makefile must list the figures for the TAR file.
(From yocto-docs rev: 6904899f2df8c531f1d6f7c61482d737b9e93971)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The fact that the Local Yocto Project release does not provide any
compatible layers confuses people. Add a section about the local release
to explain what it does.
[YOCTO #9229]
(From yocto-docs rev: cc7ebcd5a66ff3041a7fdd17e697dfb60b08cadd)
Signed-off-by: Belen <belen@icarus.isw.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hob and the packageinfo class have now been removed from the
code base. This patch removes all references to:
* Hob
* meta-hob
* packageinfo and
* BBLAYERS_NON_REMOVABLE
from the documentation.
So long, Hob, and thanks for all the fish.
(From yocto-docs rev: 6a1ba2761d5c2ec1072616ce3d791787f1b1b2a7)
Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added wording to note that include/require checks the current
directory in addition to BBPATH
Fixes [YOCTO #8566]
(Bitbake rev: bdad45ebe551912b055ffa349d254ae5947a3ba6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9283]
Updated the description to document conditional inherits. Provided
several examples.
(Bitbake rev: 07f97f4d913cf1c8233995152105fff6c6c7b9a0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bb.event.ParseStarted event is not processed by toasterui, but
present in event list. This causes the following error:
WARNING: Unknown event: <bb.event.ParseStarted object at ...
and non-zero return code:
WARNING: Return value is 1
(Bitbake rev: 1cc102f3d83d9467a3a3c422254333796ba95605)
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the very verbose log dump from toasterui. This generates several
megabytes of not that useful debug information and actually hinders
finding the original exception.
(Bitbake rev: a21dc134bdce2c9eb5e47c770094660f0c45c398)
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes it possible to prevent a recipe to be cached, and thus,
parsed every time.
Use with care.
[YOCTO #8853]
(Bitbake rev: 78335c1fbe5266116700c2413aac28b00423a75b)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Try a secondary file path if the first does not exist. When we get the
recipe paths and layer information from the layer index it is not a
complete path but we are usually able to reconstruct it. If the complete
real path has been discovered by building then use this instead.
[YOCTO #9206]
(Bitbake rev: 238db2e03405d259d48dfc477a276191e6a47698)
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Move the generated layer for custom recipes into the build directory.
The build directory makes more sense as this layer/recipe is generated
for a particular build/project.
(Bitbake rev: 77f3728ee6ea379bffcf73f33c26e982cb0795f4)
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't need to skip file:/// uri type locations for git repositories.
If you're using a file:/// uri you should know that it has to be a local
path.
[YOCTO #9200]
igned-off-by: Michael Wood <michael.g.wood@intel.com>
(Bitbake rev: 4d0e5804103c2d98d038b3c490cac37a73f3cc47)
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use a constant to define the name for the toaster custom images layer;
this constant is then used to identify this layer in various places.
(Bitbake rev: 2540969ec71612af7f9041cadcc401513e9b357b)
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We may have a recipe which is based on a custom image recipe that has
already been built so keep the recipe file around so that it can be read
by the generate recipe function.
(Bitbake rev: 502148fe498fe0a41ae89c9f649d3cb1253b0487)
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adds intel-corei7-64 with x86-common, this makes the x86-common
whitelist available for intel-corei7-64 bsp also.
[YOCTO #9179]
(From OE-Core rev: 34e7292fb40635cee1f1237ac3156530f8dfce37)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the upstream url used for testing cups versions after upstream website
changes.
(Bitbake rev: 5f06041d4936fc22297945bbbad7020bfa9083c6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>