Changes to the files that support building out and publishing
the Toaster User Manual:
* poky.ent - Added a new variable YOCTO_DOCS_TOAST_URL that can
be used in other manuals to link to sections with the Toaster
User Manual.
* Makefile - Added a section of code to build out the Toaster
User Manual. Currently, no eclipse support is added as I don't
think we want to cross into that development environment with
Toaster.
(From yocto-docs rev: 35ea6656265d61024d5db36a534a7250f783956a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For this commit, the manual only has a single "intro" file with
placeholder text only. Graphic for title page is in place,
stylesheet is in place, all files needed for a successful, initial
build of the new manual.
(From yocto-docs rev: 99416caa943fe6af13292b18bda53522ce3576d6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6912]
The example used to make sure builders use the same sstate
signatures regardless if they use icecc or not was incorrect.
I updated the INHERIT_DISTRO line of the example to use the
append part in the name so it appends the icecc as suggested
by the bug submitter.
Reported-by: Peter Bergin <petan679@gmail.com>
(From yocto-docs rev: 1f6b2f152202ab6e0be3026af3275f67bdb40d16)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7256]
In the "Serial Console Connection" section there was a link to
TEST_POWERCONTROL_CMD when it should have been to the
TEST_SERIALCONTROL_CMD variable.
(From yocto-docs rev: 9ec64c86bd4171a017898daa332d2a98fea0358a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The description for "tc" was described as "the called text context..."
rather than "the called test context...". Updated the description.
Fixes [YOCTO #7269]
(From yocto-docs rev: 0da4437c26225ce0302f10f7ba3c012f1f990c74)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These edits help place the two sections within the new organization
that basically splits out the devtool and quilt methods as ways
of modifying your source code.
(From yocto-docs rev: 1dc2e8783d9774bb98a30e06d114f1c9bfb85b71)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Using the 1.76.1 version in all the customization layers so
the manual revision tables will build with boxes.
(From yocto-docs rev: 85a31ef53a59d17bed23ebf57a14db507eb21338)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Put in proper front matter for the mega-manual. This effectively
creates a real title for the manual as well as a brief abstract
that explains why this behemoth exists.
(From yocto-docs rev: 26c78f0b00762846a839fbfc9ba969b7aa5d5b58)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Completed draft of the new devtool material. This commit affects
some linking and figures across the YP doc set.
* Added the build-workspace-directory.png file to both the
dev-manual and the mega-manual.
* Updated the Makefile to include the new figure in the TARFILE
for dev-manual and mega-manual.
* Re-did the section organization to pull the quilt and finding
source file out of the "Modifying Source Files" section.
(From yocto-docs rev: 4585b9fbb1636ae3c65e2e3ad2d1d6baca636e59)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mark Hatle reviewed the section and I updated some things based
off his input. A rewrite to the "Makefile-Based Projects" section
to get it technically correct. Also, removed all SDKROOT
documentation from both the adt-manual and ref-manual.
Fixes [YOCTO #7133]
(From yocto-docs rev: dd785777834611d94868a3774f2eb21ffc081b1a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7133]
Edits to add more clarification for use and role of the
cross-toolchain environment variables established when a user
runs the cross-toolchain environment setup script.
(From yocto-docs rev: 2c3fa3a838a3a8970cd112935e903c96552ed06b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the ADKROOT, GDB, CROSS_COMPILE, and CONFIGURE_FLAGS
variables to the glossary. Also added appropriate cross-reference
links from the adt-manual to those new variables.
(From yocto-docs rev: 812367e3b915b99d900b7934c4d5d409f393e814)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7133] partially
At the end of the section that first mentions running the
environment setup script for the cross-toolchain, I added a list
of environment variables that are defined as a result of running
the script.
(From yocto-docs rev: f1b66a09676d1b5c055e7ae7e7cc9a7f45cb9b67)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The note in the "Getting the ADT Installer Tarball" section has
a note that warns the user to be sure they have local.conf
properly configured before baking out the adt-installer. I
provided a linked cross-reference into the section of the
ref-manual that takes a closer look at user configuration.
(From yocto-docs rev: d13c044b65543a2f15fbda0266d2e30a14cfd19f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The intro to the "installing the ADT and Toolchains" section notes
that the user must source the cross-toolchain environment setup
script. I added a clause stating that this establishes environment
variables.
Fixes [YOCTO #7133] partially.
(From yocto-docs rev: e9777012d935ced8fd82209543569aaa70ab1832)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "User-Space Tools" section incorrectly stated that user-space
tools are provided as part of the distribution. The Yocto
Project is not a distribution. So I changed to say that they
are provided as part of the Yocto Project.
(From yocto-docs rev: 03dd97b68a1900959aa51ad6a17547822e8392fc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added text to note how this term is used, what makes up the
OE BS, and how the term "build system" is used in general.
(From yocto-docs rev: 2af0a59a84fd1cf6d23db29f470cb5644f962746)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list of terms had a "build system" term that basically
described the OpenEmbedded build system. I dumped this entry
in favor of "OpenEmbedded build system." I updated the term's
description to cover the generic term "build system" for no
confusion.
(From yocto-docs rev: 0ada8348a2ace6ce99e640d1c1f21812188151d5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This start to the script is not really necessary and is in fact
the rare case. I have removed two occurrences of it in the
"Post-Installation Scripts" section where it was used in code
as the best form to create a script.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: f7c1a1e135e8a9d76005bb6ae7b9cc2810f0af90)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a typo in this list. The "qemux86-64" should be "qemux86_64".
(From yocto-docs rev: 32f62f51c1574f3a479c12b67aeba7ebcb743a02)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the description for the SOURCE_MIRROR_FETCH variable
so that it actually made sense. The [doc] string was also
updated.
Found a typo elsewhere that was fixed when I spell-checked the
file.
(From yocto-docs rev: 609f09231815f80ea3fd800e0b5d9a4fbad110cc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on "Handling a Package Name Alias" was confusing and
wrong. We decided to eliminate it. The section was removed from
the dev-manual. The corresponding variable DISTRO_PN_ALIAS
remains for now but without the cross-reference link to the
now missing section.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 9938cdcc8488baffa4252288bf45243055e76fed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scrubbed out the occurrences of eglibc and replaced them with
glibc.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 868ceda79b1c738349e512e523c850b24f9232ca)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scrubbed the eglibc from the buildhistory directory and
also replaced with an i586 example.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: c7469f1a857f278e1adac9012d99802195e36849)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the references to eglibc and replaced them with glibc.
This involved updating the example buildhistory output with
current examples as well
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: b44cce9817191d616d51d6b1d067efc730423198)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7133]
This goes toward fixing the bug but not completing it. I have
added the following variables to the variable glossary:
SDKTARGETSYSROOT
PKG_CONFIG_PATH
CC
CXX
CPP
AS
LD
TARGET_PREFIX
AR
STRIP
OBJCOPY
OBJDUMP
RANLIB
NM
(From yocto-docs rev: c9d9e422684dad7cdc81db309235d0d1751ac88a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a Python script that a developer can run to create a .patch
file that when submitted to oe-core will update the documentation.conf
file. The update will bring the [doc] file variable descriptions
in line with what is in the ref-manual variables file.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: f9dca76a8d9be3dcdbde9229beb03f0ba3701485)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This option to the PACKAGE_CLASSES variable is broken and not
supported. I added several warnings saying such. We opted to
keep the documentation rather than eliminating it completely to
prevent questions should someone find the code and wonder why
it is not documented.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 1acf3da2034c4c3f74acee1ccb375f0450ed90a0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The way the old manual set had worded the use of the
BB_NUMBER_THREADS, PARALLEL_MAKE, and BB_NUMBER_PARSE_THREADS
had become depricated. It suggested a lot of user intervention
to get these variables set to have the build system utilize
optimal parallelism. The change a while back to the build system
where the variables are set to the number of build host cores
now makes the variables automatically be set to their best
values. I have gone through the manual set and changed wordings
appropriately to reflect this.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 3a27b1792c92a2f22173315e2732f672cdad2c78)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Speeding Up the Build" section presents a list of items the
user can consider when they want to tweak the build speed. One of
the items is the three variables BB_NUMBER_THREADS, BB_NUMBER_PARSE_THREADS,
and PARALLEL_MAKE. It was noted that the system figures out
the optimal settings for these now and it is pretty useless to
override the settings. However, the introducing sentence to the
list is still valid due to other considerations that go beyond these
three variables. So, to update the text, I have re-emphasized the
role of these three variables for quickening the build time.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 84610550cef66d0aa7478bcf95ad97b081709b2f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example was out of date. Updated accordingly.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: b95535fca149abbbe4fee7e74ebc13d2bb376c27)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated some text to indicate that you should put patch files
in $BP, $BPN, or "files." Also, added more on how the patch
files suffix is (i.e. accounting for compressed suffix names
like diff.bz).
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: d9e23da24e9d86ec5e2b9d4067667478f3e56ba1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch files can end with compressed suffixes such as
diff.gz and patch.bz2.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 69993710d1466dddc804c33c1d76f46d0982d28f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Fetching Code" section, some loose description of how the
build system reacts to the two checksums in a recipe existed.
Robert asked some questions about how the behavior would be if
just a single, correct checksum existed and if the two existed but
only one proved correct. Turns out, if you supply a single one then
the build will not throw an error or warning. If you supply two
but one is incorrect, then the build will throw an error or
warning. I updated the text to be technically correct without
going into huge details.
(From yocto-docs rev: f49a744821d9326314803d5003158bd402e74e0d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor edits to the original patch. These edits were caught by
Robert P. J. Day.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: b50a2e44eccd50166351611f17c643cbbc60f8b8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Placed a reference for more information on the variable into the
section of the dev-manual that explains how to choose a device
manager.
(From yocto-docs rev: 3f9b1329fe4794af03d673323d11558e85d9b097)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch was modified to fit in with the style of the book.
(From yocto-docs rev: 7c6c7ac573f92bfc844977e0d7a97ca4aac9bc70)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had it out of order alphabetically.
(From yocto-docs rev: d766cc58dfe2581599815b76729c742034c910ef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bob Cochran pointed out that the skeleton recipe shown in the
example is not really what is created by newbb.vim. I updated the
example to match.
(From yocto-docs rev: 2dfa712522aec5204b9e739b6060109090280011)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was a bit confusing on the use of "_prepend" as associated
with the FILESEXTRAPATHS statement. Especially in the final note
where it indicated you don't need "_prepend" if your append file
is not adding any new files. I updated the note to be more specific.
Another small change I made was to replace the Crown Bay BSP referenced
in the section with the Emenlow BSP, which has a longer life span than
CB.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 35bdc8031bc4ecf1ea321b0cafade97eeaa56513)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When you "make" the mega-manual, there were four tags across the
various manuals where the same string "id='intro'" occurred. This
causes warnings during the make process. I updated the strings to
be unique. There are no cross-references to these so no collateral
issues were caused.
(From yocto-docs rev: d0e770e0ad797031a75e2373a41723408b4b051c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the following variables based on slight review changes
from Paul Eggleton:
EXTRA_AUTORECONF - changed autoconf class to autotools
KERNEL_IMAGE_MAXSIZE - Wording tweak
AUTO_LIBNAME_PKGS - Wording tweak
DEBIANNAME - [doc] string updated
TCLIBCAPPEND - Second clarifying sentence in first para added
PACKAGEGROUP_DISABLE_COMPLEMENTARY - [doc] string updated
(From yocto-docs rev: ff5c765ffab1cdf6fc8a007cebdf7114432f65ef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section "Customizing Images Using Custom IMAGE_FEATURES
and EXTRA_IMAGE_FEATURES" needed a bit more clarification on
the image features. The text pretty much passed off image
features as all mapping into package groups, which is not true.
Some, like "debug-tweaks for example, are more like general
configurations. I updated the section accordingly.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 7dd55ff0bd6f7923e22695ed7323df5cfe17d1d4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This note provides a bit of a warning or tip regarding naming
BSP layers. The letter of the law dictates that you don't
need to prepend a BSP layer name with the string "meta-".
However, scripts exist in OE where the naming convention is
assumed.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0375349fdd3cd5ff8a54db8124d5cdc02133ff12)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7029]
I was missing the "sysroots" part of the path. I added this
to the pathname.
(From yocto-docs rev: 077efc8063ed01ef4067f7e71912dd52c1f6a4a6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Crown Bay is short on life so I swapped it out for the eMenlow.
(From yocto-docs rev: 6d5394c12a374463cb1d5215af88178b63a5b8c0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The yocto-bsp and yocto-kernel tool output for the examples
were updated to be current.
(From yocto-docs rev: a05b1df35c7518027b1eb73f9ea2b6a3d00dca43)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added descriptions for the following variables:
EXTRA_AUTORECONF
KERNEL_IMAGE_MAXSIZE
UPDATERCPN
AUTO_LIBNAME_PKGS
DEBIANNAME
DEBIAN_NOAUTONAME
TCLIBCAPPEND
PACKAGEGROUP_DISABLE_COMPLEMENTARY
CLEANBROKEN
DISTRO_CODENAME
BASE_WORKDIR
DISTRO_FEATURES_DEFAULT
DISTRO_FEATURES_LIBC
Part of adding new variables is checking to see if a previously
undocumented variable is used elsewhere in the manual. One
occurrence was spotted and turned into a link for this list.
(From yocto-docs rev: bb75387b7aa4fcb0b594d300772952d81a651644)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default, making a file will not include the PDF version of the
manual. Some manuals you can't do a PDF version anyway (i.e.
yocto-project-qs and mega-manual). The PDF versions do not need
to be part of the mainstream make process. If someone wants these
they can take the extra step of doing 'make pdf DOC=<manual>'.
(From yocto-docs rev: 16f605350adb1b252b94e921faf282d0634cefb6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Covering CentOs to 6.x and the debian stuff to 7.x
(From yocto-docs rev: fa7d6f138506b90330c52c1dbe3a56e40a34a97e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I need to get back to how it was working and then fix the table
box issue from there. Using the 1.76.1 stylesheets makes the
build too long for the manuals and sometimes the XSL sheets do
not load.
(From yocto-docs rev: 7bc502fa069fdc4aebf5705513bb82127716859f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was pointing to a poor example in meta. I substituted
in a better example and rewrote the section to flow better around
that example and the final fabricated one.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: c7f07a2993d5c1b8e0c8b7da0e9d4c28242a5e26)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a sample string in this tree that ended in "ro" when it
should have been "r0" (as in release 0). Anytime you update a figure,
the modified file must go in both the "figures" directory of both
the manual (dev-manual in this case) and in the mega-manual.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 8e75cc23fbf03f355fade416a12b7c8fe1e656a5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: ea4489f856417d70b54a7e38da32e068cbd54cbf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I applied (in spirit) the changes here... Some literal and some
with changes.
(From yocto-docs rev: 0ccf8a43264981accbe42f729c723804e5b69b72)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The way the explanation for adding the BSP-specific files did
not take into account for layers that might support multiple
machines versus a layer not supporting multiple machines. I added
more explanation that covers both scenarios to be clear.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 3f00f0bb830665f8711c68aa6110b8399e867345)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Crown Bay BSP now only supports VESA graphics. Because of
this, some of the examples in several areas of the BSP hierarchy
were wrong. Changed accordingly.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: b61f013a086a9135a86eedf2884fd1b07f798165)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the choices and version numbers of the "yocto-bsp" section
of the BSP guide to match the current development utilities.
(From yocto-docs rev: 0f8472ffa2bc3ae762587c4e2345a4d9850608ed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The directory structure no longer seems to support two flavors
of the BSP: one with EMGD and the "noemgd." Only the "noemgd"
remains. I have updated some of the examples here to reflect
the current directory structure and sample configuration code
for the BSP.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 64fc4a7a6d69eb99dcd3d8c5e388810e7052ad75)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* small number of typos fixed.
* documentation corrected in a couple places.
* for most part, reduce line lengths to 80 for printing.
I was going to fix just a couple typos, then figured that while i was
there, might as well do some cleanup, mostly in the area of reducing
line lengths to 80 where possible for printing. feel free to comment
on any other possible aesthetic fixes, i can add them and resubmit.
(From yocto-docs rev: cfe4c061d8691e128933b81693aa42c809ef5486)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes the issue where the lines for the manual revision table
are not appearing. For some reason they do not appear when building
the docs using Ubuntu 14.10 and the "current" XSL transformation
files. So, I backed up to the 1.76.1 version, which is the nearest
version where the issue does not surface.
(From yocto-docs rev: 82b15986b97b9ed082b652b562eaaf843572fdff)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update entry for IMAGE_BOOT_FILES with information on glob
patterns.
(From yocto-docs rev: ad3fc0061e3f4dc3ecc6b0a101685c301c5690e9)
Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5463]
Updated the notes in the TUNE_ASARGS, TUNE_CCARGS, and
TUNE_LDARGS to indicate that the BSPs select the tune and then
selected tun affects the tun variables themselves.
Also combined the TUNE_PKGARCH and the TUNE_PKGARCH_tune variable.
We really don't need the TUNE_PKGARCH_tune variable as it is simply
the TUNE_PKGARCH variable with the override.
(From yocto-docs rev: dabc624272a9bb4cf5e62dee664ba729a9887208)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit 914c482bd89071ab34b3381e3bd8065f871cc047.
I had to revert this change because it broke the footnote behavior.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Creation of a PDF version of the YP Quick Start is not supported.
The <mediaobject></mediaobject> code appears in the manual for
that purpose only. It is ignored during HTML generation. Thus,
I have removed it from the file. The image is actually displayed
through the <authorgroup> definition, which is located in the
CSS stylesheet.
(From yocto-docs rev: 322ae6450dfac9b2054b33334898a078fdd20902)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I discovered some artifacts and inconsistencies with how the YP
Quick Start was made. I made the following changes:
1. Changed the structure of the QS from "article" to "book"
as it is a separate book. This change doesn't fix anything
but it does bring the XML file closer to passing validation.
2. Removed the <abstract></abstract> tag. This tag was in place
simply to display the PNG file for the Yocto logo in the upper
right part of the first page. After turning the QS into a
book from an article, the title could be displayed as a PNG
file similar to the other books. This change solved two issues:
1) removed the empty "abstract" element from being displayed in
both the mega-manual and the PDF version, and 2), brought the
author and look of the first page into line with other YP
manuals.
3. Removed the old PNG file used to display the Yocto logo at
the top of the QS. This file was removed from both the
yocto-project-qs and mega-manual "figures" directories.
4. Added a new "yocto-project-qs-title.png" file to both the
yocto-project-qs and mega-manual "figures" directories.
5. Updated the "qs-style.css" file's .authorgroup element to
match and behave like the other YP manuals. This effectively
correctly displays the title PNG file for the QS.
6. Updated the Makefile area where the TAR files are made for
both the yocto-project-qs and the mega-manual. I had to
substitute in the new PNG file for the QS one and had to
add the title PNG to the mega-manual part.
(From yocto-docs rev: 914c482bd89071ab34b3381e3bd8065f871cc047)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The DocBook type at the top of the file indicated chapter
when the actual block of XML is article. I changed it to article
to be consistent.
(From yocto-docs rev: 5350426c11abc2fa4b1418a2d215cd8814745ef9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the example that creates a new BSP layer by using the yocto-bsp
script, the final step 6 could be interpreted as the script
creating the new layer in "poky". Even though the sentence is
technically correct, sloppy reading could mis-interpret it. I updated
the sentence so that nobody will be confused.
(From yocto-docs rev: 7c2bed2aa6f8c189ed9cabff6e4d4d9557238702)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6158]
Updated the style scheet file to format glossary variables in
such a way to allow for a PNG file of standard size to be
displayed below each variable. Right now, the PNG file is a
generic placeholder. Each variable displays a PNG file.
Updated each variable to include that PNG file.
(From yocto-docs rev: 24b7b847b7093022a49a014395df0c3a8c019331)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5400]
Per Martin Jansa, added some information in the bullet item that
talks about the tools and the cases that can cause issues when
tuning things by machine or architecture.
(From yocto-docs rev: e8e47828df65abdc18bbd681c47719a7df77b00f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5400]
I applied some review edits to this section as suggested by
Richard Purdie.
(From yocto-docs rev: a1898cf65537e732e0e42605bb28d636077e7f56)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5600]
Added a <info></info> tag pair with a short description of the
variable to each variable in the glossary. The short description
is what will be used in the documentation.conf file. Scripting
from engineering will pick up the variable description
automatically. The information between the tags does not
appear in the HTML or PDF output.
(From yocto-docs rev: 57fb9100e377a96c330be20613c5895b25910022)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5400]
This is the first draft of a new section on multi-machine builds.
(From yocto-docs rev: a47fd17295d943bff482a0747f3b2e69831aa985)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The LTTng Documentation website has been updated to actually
have extensive documentation now. Previously, in the profile-manual,
we were stating that documentation did not exist, which was true
at the time of writing. I updated the section to link to the
main LTTng documentation website and altered some other text in
the section appropriately.
Additionally, I found and corrected a couple spelling errors in
this chapter.
(From yocto-docs rev: 6e03bd6b90726904a1ac54b8f16f6554b4bb22b8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replaced the 1.7 strings with 1.8 so that all links in the
mega-manual are self-contained and properly resolve.
(From yocto-docs rev: 49f4b02c999ff2c3c78111673f6760f5fde2b82e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added an entry for the 1.8 release stating that the release
is slated for sometime in 2015.
(From yocto-docs rev: 9799a7848f24024048eae0cbed470a2be4b4b879)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor wording changes and a new section added for local.conf
QEMU changes. Also, reordered some sections.
(From yocto-docs rev: 65207b6afa6df7d82cd3482d61f10b308da6fac7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the section to account for some new variables and
several more ways to run tests against expanded targets. Also
added power control section.
(From yocto-docs rev: a0f08466c00ae51a99d790fa6c9dccef2e0f1518)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added Debian 7.5 and 7.6 to the list.
(From yocto-docs rev: 35fd5d5399fe1759158aef19d7b6eb68f2a1af12)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied the third set of review comments from Paul Eggleton to
some variables.
(From yocto-docs rev: 2be5bc26a6fda1922ee73a874522180633d33b98)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For consistency, I changed the introductory sentence to the
variables that function when inherited.
(From yocto-docs rev: 6ba4fe635c45abf7692f4be0a09ede89a89ec9fa)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These edits were minor with the addition of some descriptions that
had to be fleshed out. All comments from Paul Eggleton.
(From yocto-docs rev: 4ae7c5a5e5aa23307e28de0832d379145c4ef8f1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added ASSUME_PROVIDED and SANITY_REQUIRED_UTILITIES variable
place-holders. There is no text there yet but they are there
for placeholders.
(From yocto-docs rev: adfa77dc597303dcff0e95fd4b3ffd5ae2fb08d5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also fixed an error in the compress_doc class.
(From yocto-docs rev: 3c3532ec4f3ab5985ea3c2f3689ab5cdb7e16bad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Improved the formatting of the two examples that show where
sysroots are written.
(From yocto-docs rev: 7807e8a727e1e70c2537ac9ead2ad15305c656ca)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a single occurrance of this that used angled brackets
to denote the target (e.g. <target>). I replaced the formatting
with the <replaceable></replaceable> tags for consistency.
(From yocto-docs rev: 4e013136c27d68f89854e78cbf354583d51aa2a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the manual I was using angled brackets to denote user-supplied
input values. This was confusing so I changed to using the
<replaceable></replaceable> tag pair.
(From yocto-docs rev: dc73a78f11038a1ff04b16867e7513f31f02374b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Throughout the manual I was using angled brackets to denote
user-supplied input. This is confusing so I changed to using
the <replaceable></replaceable> tag set.
(From yocto-docs rev: 79ec3f1b1330539ab2b3bdfb1c94e58c2d0feead)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Throughout the manual I had been using angled bracket sets to
denote user-supplied input. This is confusing and better shown
by using the <replaceable></replaceable> tags. I scrubbed all
the chapters and replaced as needed.
Some other minor formatting changes were caught and fixed during
the scrub as well.
(From yocto-docs rev: 9a668574dd18828a750cfa2e8c28e1f089a19609)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the new QA Warnings and Messages chapter to the list.
(From yocto-docs rev: aab515c793107b7c0b3a8a26f522cf26461fd3d4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed some minor issues with build-deps and file-rdeps.
(From yocto-docs rev: b4250c9ba7d6a3d30c3dfb94d9e2e2eea6b47764)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Forgot the word "class".
(From yocto-docs rev: e54102d2a5df3f703e4ab23ed9062ef2abf7315b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to change wording to state that the class uses out-of-tree
builds.
(From yocto-docs rev: 2fbaeba33988e14a97d5946f7e714a1bbc5a3ccb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied the second round of review edits from Paul Eggleton.
Minor fixes.
(From yocto-docs rev: 2c7c45c8f09b724e92e8b59fe47834226b44b4fb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied the full set of first draft revision edits for the
new migration section for 1.7. Comments from Paul Eggleton.
(From yocto-docs rev: 90586addbc719ecaf7c768b267adf0e988e27b74)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure needed to be updated to reflect that build-id.txt
is now part of the tree and not build-id.
The publication scheme dictates that figures are kept in
individual manuals and in the mega-manual figures directory.
(From yocto-docs rev: 0711a3e41c42eb058db25ff2ea7f1c0982e06963)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This file is what is written now rather than build-id. I changed
the file name and noted that it also contains the full build
header information as written out by BitBake during the build.
(From yocto-docs rev: 7e55b4b5f9e27f6ac5d8f1eab4923bf1b8a712c6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I removed the linux-yocto 3.4 kernel from the list in the
section describing which kernels we support. Also, added
the 3.17 linux-yocto kernel to the list.
(From yocto-docs rev: 41f57a9abe1201ed2fb657f8441c97f86f75200a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable has been replaced by the KERNEL_MODULE_AUTOLOAD
variable. I updated the description to note that and to provide
a cross-reference to the new variable.
(From yocto-docs rev: 8b2f464f7d100db1c585ccc62d7cab89f7f7b164)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added this description to the variables glossary.
(From yocto-docs rev: 3da322f92d5028e96422e0c1f5df78b285f2355e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added this new variable to the variable glossary.
(From yocto-docs rev: d2d75631777f6cef3472bde428ed65419c99457e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This description was a bit confusing with the way the general
syntax was described so I re-wrote it a bit. Also, added the
requirement that if you use module_conf for a given <modname>,
then you must also include the <modname> as part of the new
KERNEL_MODULE_PROBECONF variable.
(From yocto-docs rev: 15b7819a0d9946ad6565576a6f28897e2dd724f9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the ref-qa-checks.xml chapter so that each QA warning
or error message would generate a permalink that is suitable
for searching from the poky codebase. To implement this, I
had to embed an id marker in the <para> tag that precedes each
<code></code> tag pair. The 'xxx' string of the id is the leaf
portion of the permalink.
This creates the following tag construct:
<para id='xxx'>
<code>
some-warning-or-error-message
</code>
</para>
The permalink is generated with the help of the new
qa-code-permalinks.xsl file, which triggers on the
<para><code></code></para> construct. This new file resides
in documentation/template.
Right now, this construct
is unique to the ref-manual's chapter on the QA error and warnings
chapter only. However, if for some reason that construct is
used in any other part of the ref-manual, a generically numbered
permalink would also be generated.
The ref-manual-customization.xsl file was also altered to include
the new documentation/template/qa-code-permalinks.xsl file.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: aec27a9f8337575d31bfe0066563da99259046e0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added "October 2014" to table for all manuals that have the
table.
(From yocto-docs rev: 3f9ceb4dd2397fe907bf701c842277eb65d11a56)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reversed order of the list presentation and re-worded the static
library sentence.
(From yocto-docs rev: 5c32730550629527f6ceb2140df31a097f7a6081)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the section to have two lists of features. One list
is for features that work only when you inherit the core-image
class. The other list is for features that are available for
all images regargless of inheriting this class.
(From yocto-docs rev: 9d1bcab2a9264e64db2dec66247aaf55493ae362)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list of features in the section was out of sync with the list
of features shown in the comments of the core-image class.
Additionally, four of the features are available to all images
regardless of whether or not the core-image class is inherited.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: e4821fd0a63e906da8b1ff015fb4970e5e62d667)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the following:
efi
pcbios
phone
qvga
rtc
vfat
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: b3fe96df8552921cb6494a72d721fa6b41a70a3b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a space-separated list and not a comma-separated list.
(From yocto-docs rev: 23cf09ac128289e878bbc056e28060008ab5217c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a small sentence to note that this class is a good class
to use for extracting and installing propretary binaries.
(From yocto-docs rev: adde5e66f46df0b4e21bfe0fc0b47a9a8bed5e0c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Corrected some wording and also the first example.
(From yocto-docs rev: d641cdbf697b14d8122b3a018b06eed3437011ad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bulleted item on supported BSPs was very centric on meta-intel.
I rewrote the section to not be so exclusive.
(From yocto-docs rev: d8118bb6124fbbb2340ae8720cd6187fd5546967)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5482]
Added a cross-reference to the meta-selinux layer in the section
that describes how to make images more secure.
(From yocto-docs rev: 0c96273ee857808046c5a76517c1eda4aa703c81)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a short note after the example that shows how to set up
the EXTERNALSRC variables stating that the externalsrc class
needs to be either globally or locally inherited.
(From yocto-docs rev: db935135c0b060e06f6a63530df995d286002598)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new example on how to set this from the recipe or the
recipe's bbappend file.
(From yocto-docs rev: bc0d9de3378f3462729301e74419b7dede17558b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found another occurrance of where I needed to add a <replaceable>
tag set in an example.
(From yocto-docs rev: 586e5a590bb5382a28fde4670fdcd6cbb75f6c32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I missed a <replaceable> tag set on the example. Adding it
clears up confusion for how to use the variable.
(From yocto-docs rev: 8bbf2a012e580d82aaf9c9a98ad5dab1aea64f7b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was confusion about how this actually worked when you
do not create a package for a package listed with the variable.
Cases for when the build would throw an error or not had to
be clarified.
(From yocto-docs rev: 02f95339322afe53db816b3b73234490d835b1ca)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Added some text associated with the screencast we link to that
calls out the fact that the screencast is somewhat dated but
still useful.
* Replaced all user input in examples so that they are formatted
using the <replaceable></replaceable> tags.
* Fixed a few places so that they use better and clearer wording.
(From yocto-docs rev: f99536a7581ef9b8b57a446b65e4ebb902b4e4b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Found and fixed several areas with issues.
* Scrubbed for user-supplied input to make it use the
<replaceable></replaceable> tags.
(From yocto-docs rev: 0e1c7ad31921ee7d4ee0d7d4ece01303a25a5d60)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6621]
Applied a few review edits for this fix.
(From yocto-docs rev: 99511bbcfa1de2f7bf691da1a002913f3a7f6034)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6629]
Added a new variable description to the glossary and also updated
the IMAGE_LINGUAS entry to have a back-reference to the new
variable.
Reported-by: Laszlo Papp <lpapp@kde.org>
(From yocto-docs rev: 219097735c57a3dc10195511dd5b199e73b8a094)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6621]
This is a new variable that helps control how debug symbols and
source files are split off when creating -dbg files for use with
GDB.
(From yocto-docs rev: 506b79707f6aec7c14f1f9d7e5099d20fca45c0e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For firewall performance.
(From yocto-docs rev: a866449b4caf1c0cee4ce00ec7d8fa2119a0b481)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I replaced user-supplied variables with <replaceable></replaceable>
tags to get proper formatting. I inserted several references
to the new QEMU chapter for help using QEMU. I updated a note
on the BSP available so that it is a bit more generic and not so
dependent on an exact list within meta-intel and the source
repositories.
(From yocto-docs rev: daef4406e7c3e45dd5d98d565e519d91939f6965)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replaced angled bracket items for user-supplied variables
with the <replaceable></replaceable> tags.
(From yocto-docs rev: 393af6c0cfbfc0f3921bc1eb1fdbd3dd734f51ae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some links and fixed up some replaceable items.
(From yocto-docs rev: 5c9ce934f13c68c2efbd952f399a8b88e87eb761)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6620]
I altered the path name of the .gdbinit file in the text to prepend
~/ to it to reinforce what file the user must modify. I also removed
the /home/jzhang string in favor of ~ to make it more general.
(From yocto-docs rev: ff09d3a5666c97598adf385f63dee4b30b0f1792)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I'm guessing that the OE wiki page for bitbake is the closest thing
there is to an "official" bitbake web page, so i'll just use that as a
replacement for all berlios.de links i run across, unless someone has
a better suggestion.
(From yocto-docs rev: 36bafb65e96752631d71afca86dcebda6ba1a876)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This list has grown substantially and it is impractical to list
the directories that contain image recipes out. I left the
"ls" command that the use could run in order to see those
directories. This makes the section of the manual much more
maintainable.
(From yocto-docs rev: ee129f578dfa986937b45b111e0e26b61b42c565)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The image list has grown to where it probably could use some
structure. I ordered the list by alphabet.
(From yocto-docs rev: 4ee03974d9a58d2b49af3ae4cafe9ac181627c86)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added this image to the list of images in the "Image" chapter.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 29161a98f2bacc6fac77fcb11c2bfe1c905167f8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The initrd image used by the Linux kernel is list of file
system images concatenated together and presented as a single
initrd file at boot time.
So far the initrd is a single filesystem image. But in cases
like to support early microcode loading, the initrd image need
to have multiple filesystem images concatenated together.
This commit is extending the INITRD variable from a single
filesystem image to a list of filesystem images to satisfy
the need mentioned above.
(From yocto-docs rev: 051ef2e4d6480b28d21a59a79b6f0dca1a5944bd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the "svk" protocol and added in the ClearCase one.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 21b241990dec9b7beeeec639ac6c6e9b22f2b871)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor review edits from Max.
(From yocto-docs rev: c70de50aeceda60db92c5e488bde8fe910eaeba1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Edits from Paul to better word this section.
(From yocto-docs rev: 51425ab506050ee5ba30d5c3c10639d5a1b8cc8e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These catches are from Robert P. J. Day and applied as a
patch.
(From yocto-docs rev: b805795e9bf68286aa5b79a94792e2fefd293b92)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Accidentally put in a couple different things in this one commit.
Oh well.
1. New wording for how the user needs to figure out some checksums
for a recipe.
2. Fixed up some note placement in the wic reference section.
(From yocto-docs rev: 6c13f49c265c99ddd6dcd4ec3c3c8e66b78824e0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
One has to do with the weird names the build system creates based
on DESTDIR and other variables.
The other has to do with -native recipes not buiding correctly.
(From yocto-docs rev: 32a444a258e3c7c87fdc015475f54e5b34628246)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #641]
Added a new bullet to the list that overviews what the manual
covers.
(From yocto-docs rev: 54bdb50df3951346a2e926700681db55bd59a2e1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pulled a note about future support of commands and options from
the bootloader section and got it up in the higher level intro
section for that part of the manual.
(From yocto-docs rev: f8d677301abcd0d549ea9ad4cca79f43cb2db7f0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #641]
New chapter added that covers the YP instance of QEMU.
(From yocto-docs rev: 7ca17d02364af7e5924e23df6c138ab4dd2203d6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on wrting a new recipe suggested using a "build-fail"
method to get bitbake to return exact checksums for code. It
was pointed out that this could be a middle-security risk and
that we should not do that but instead get the signatures from
the upstream website. However, many times those sites don't
provide that information. I re-worded the text to note the
ideal method (upstream checksums) and then resorted to the
"build-fail" method as a "way" to also get them when the upstream
location does not have them.
(From yocto-docs rev: b06699de2f512b01600bf952a8ee928c2a4c358a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made some small edits to the section based on Tom Zanussi's
review.
(From yocto-docs rev: 560ea7b0eb131e59b190a34cadbe77729e76d61c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a bogus link in there to the Build Appliance page.
I also noted many links that use the <ulink> tag that crossed
multiple lines. That is not good. I cleaned all that up.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a39cea47cae29d7efb8e12495e8eefb484d464c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a set of fixes for miscellaneous dev-manual updates noticed
while transcribing wic help for the dev manual.
(From yocto-docs rev: fd2205e2778e2cef86561025fd904f303d64586a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
--fsoptions support was recently added to wic, so document it.
(From yocto-docs rev: 91efb698eea438083474c1e905dbaad3fffdbd81)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
squashfs support was recently added to wic, so document it.
(From yocto-docs rev: 22ca1141953b4fae92e15126da296d3d95e80c25)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new section discussing plugins, taken directly from the
corresponding wic help section.
(From yocto-docs rev: c1b4c378a496413f2dde8ad2f043a537cba24b6e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6511]
Added a new example to this section that shows how to package
up binaries so that you can add them to an image.
(From yocto-docs rev: e52acc444c8f142d0469d7274fb936b5242306ec)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add in a few links to member orgs, and update the BitBake link.
(From yocto-docs rev: 481c89e9b8e219358db8bfdfff0b5b0150247c07)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recipe should be named "foo_1.3.0.bb" instead of
"foo_1.3.0-r0.bb".
(From yocto-docs rev: c34c3ea05d550fc85ab04036856704a7c04fd64c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We want to encourage installation of the buildtools tarball for
getting the most up-to-date packages on this build host.
(From yocto-docs rev: 5298737a5ad579ea5097221d2ef5a0f388ebff6c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the section on 'wic'. I have dropped in the same exact
section from the 1.5.3 (dora branch) release as a starting point
for Tom Zanussi to scrub and update for the master branch.
(From yocto-docs rev: e189992bff4249664ba959b1c440541e0b84e03d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6499]
Fixed a couple example INCOMPATIBLE_LICENSE examples so that
they now use the canonical licensing names GPL-3.0 LGPL-3.0 AGPL-3.0.
(From yocto-docs rev: d2d6be323d1a5ed9da88b7924954f9733a78da84)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replaced with packagegroup names, the newer form.
(From yocto-docs rev: 5492b0669acc9ce8a8ee1a00dfdc7e9f2b98a5c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* INITSCRIPT_PARAMS - noted the default
* INITRD_IMAGE - added a reference into the image-live class.
(From yocto-docs rev: 152cb93ca591c46a1344f2f09e0f85f14519ddf3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The note did not need to be there.
(From yocto-docs rev: 5ff94a1a412447c1ed1cda64e985b52545ccd9e7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found an occurrence where we were refering to the removed
task do_package_write. I changed it to "do_package_write_*"
(From yocto-docs rev: 4e989f2df1cf74c81ba9d02088addb79012762a7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6499]
Updated three areas to include similarly licenced components
regarding the use of non-GPLv3 licensing.
(From yocto-docs rev: 88c0720e4070be58fbde17bc04db2b53c3307bf8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Discovered that the sed file was processing the bitbake-user-manual
just like the others, which was wrong. the BB manual is not included
in the mega-manual so the links there need to be left alone. The fix
included specially creating substitution lines to handle all the YP
docs while excluding the BB manual.
(From yocto-docs rev: f2c99c6a66c3f67ab226f317dfae195294ddafea)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed a reference that was not linking to the manual but
was instead referencing the Source Directory structure.
(From yocto-docs rev: aae3fb868e95ef2dbd548a5f9d1ea61a013190cd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Conflicts:
documentation/ref-manual/ref-variables.xml
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added several cross-link references for the LICENSE_FLAGS and
LICENSE_FLAGS_WHITELIST variables. Note that the cross-references
previously put in for LICENSE_FLAGS were slightly wrong as they
were using the <ulink> tag instead of the <link> tag.
(From yocto-docs rev: dc2769c63d24d3650c993cfd48bcb4540ad36ca2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to add several links to the newly described
LICENSE_FLAGS variable in the glossary. Three links added to the
ref-manual and a single link added to the BSP Guide.
(From yocto-docs rev: 2ca6e556c299814d6ef847ed059a4f0a2d48adb3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the ref-manual, I added a new variable description for the
PTEST_ENABLED variable.
In the dev-manual, I added a note to the "Adding ptest to Your
Build" section to mention that the OpenEmbedded system uses
PTEST_ENABLED to enable or disable building ptests and that
the user does not set this variable directly.
(From yocto-docs rev: 52d6608caaa25378b873e41e1ddd05356ff8629a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a bit about values being passed through the
update-rc.d command and then a reference to the command's
page.
(From yocto-docs rev: e007414608ed801e440b701d6c43dca955a11611)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* For "Architecture did not match" and "Bit size did not
match", added the missing QA check name marker [arch]
* Under the already-stripped entry, added a final sentence
(to the paragraph before the note box)
(From yocto-docs rev: 7c3bda03a4424d1e083403266c570b34fcab9bbf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the link into the section for understanding how
OVERRIDES work.
(From yocto-docs rev: f897b9d0cc51899f3e4ce05b69a3c1dd429780d7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section heading in the BitBake User Manual changed.
Consequently, the lone reference in the YP doc set to that old
section became incorrect. Fixed the link.
(From yocto-docs rev: f4ecea15d62fd0eed83f03d370b20bde95f3936d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
More detail added.
(From yocto-docs rev: 84177a600f84af4cc41b9493b46e2a23bc7ccc19)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5772]
Updated the customization layer to include the file that generates
permalinks for the variable definitions.
(From yocto-docs rev: 4b981d3fe30b609b08f22ee0e1e03eee6dcc0b5d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5772]
Updated each manual's CSS style sheet to contain a style for
how the permalink symbol looks on its own and how it looks
when a user hovers over it with the mouse.
(From yocto-docs rev: c8d4afa0b83a40ac2de0c47c191a11b3e7d241e5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5772]
Updated the customization layer to include the file that generates
permalinks for the variable definitions.
(From yocto-docs rev: adfb6f06fcba2045e56353bcff0df1df9106544c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5772]
With this template, all that is necessary to trigger permalink
generation for variable entries in a manual's glossary is to
update the customization layer to include the gloss-permalinks.xsl
file.
(From yocto-docs rev: aebe1a727be7921fe9bc26101b670d5fdc1670e4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5463]
In addition to adding these two new variables, I did some cleanup
of the TUNEABI variable description for consistency.
(From yocto-docs rev: cf5c5fd0cb262b8da030ac923fda902d9e007b21)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New glossary entries.
(From yocto-docs rev: dbf566e1009d51ad8fce1ac8251249a70fb9270c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New variables added to the glossary.
(From yocto-docs rev: 903ed6d26d7d32e4c1237fa9fd44b7471f1a41f2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO 5463]
Added the TUNE_ARCH variable. Also placed a cross-reference to
TUNE_ARCH in the TARGET_ARCH variable.
(From yocto-docs rev: 85d2a49323e0040b263b6d7f08fd036a25297b05)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These types of references cannot span multiple lines. If they
do then mega-manual.sed will not process the link in the
mega-manual.html file.
(From yocto-docs rev: 8a06542c0f1fee503eda12052adddaaf9c94ca91)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This line was left out for links with no target. The line is now
in there.
(From yocto-docs rev: 5a27a32261628b7d4f60981cfe624f08d8cf1535)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1949]
Updated the following tasks to note that they "clean" out some
areas when run:
do_populate_sysroot
do_deploy
Also made some notes to the do_cleansstate task about attempting
to clean remote mirrors.
And, made a change to do_cleanall to specifically mention that
DL_DIR is cleaned.
(From yocto-docs rev: 7e532b17ccd89e43d3661c733ce1f06a52066c29)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5566]
For the dev-manual, I created a new section called "Working
with Source Files." In the section, I cover how to set up mirrors
and also how to pre-fetch source using the bitbake -c fetchall
<target> command.
For the yocto-project-qs, I removed the mirror information in the
"Super User" section, which became redundant with the new section
now in the dev-manual. I also, removed the fetchall variation of
the bitbake command. Both areas reference into the new section of
the dev-manual now.
(From yocto-docs rev: f314061e3e752d35ea85ed16a60f7f9292180921)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #3729]
I made an editing pass through this section. Found some minor
corrections.
(From yocto-docs rev: 314ec3a066de7328b6c6893ce33cc0e5faa8700a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5895]
Some minor edits to the section. I found a grammar error and a
mis-wording.
(From yocto-docs rev: 86e85512279a1379d9b30825d6af3e508faa320a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #4958]
Added a new section to start the Migration chapter. This
section will hold general migration issues that are not tied
to a specific release.
(From yocto-docs rev: e78ae7c64ae5fa7e7a5b1f804fb40b5690a4e899)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul reported that "buildimg" was being used as the class name where
it should have been "bootimg". Not quite sure how this slipped through
but it has been fixed now. There were five occurrences.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: fdd6a6725bd22e4272a99a3da179cd69c4a221a1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a note at the end of the section to point to a wiki page
with more information.
(From yocto-docs rev: ba310c34844e9e496d7ff1164691930d4f330f93)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was a stale link. Updated to point to the published
HTML file now and to mention that you can find it in the
Source directory.
(From yocto-docs rev: bc51935372cfd81a77f201768173d8b1eb1677c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I scrubbed the manual set for appropriate places to reference into the
do_clean* type tasks. Found and added several occurrences.
(From yocto-docs rev: 01594823b1d556bc70e928af1838039cc15a816d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6430]
The style sheets were carrying over old .PNG files that are not
part of the manuals. I have removed the statements that were
using them.
(From yocto-docs rev: 6e4fa419b9367ab5e34b9aa8010a24980416dc7d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6400]
Replaced the sentence in the note to specifically note that the
genericx86-64 BSP has been added for 64-bit Atom systems.
(From yocto-docs rev: ad2cbe806580c880708e5e60435046b07258a537)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a ptest section to the "Moving to the Yocto Project 1.6 Release" section.
Fixes [YOCTO #6400]
Added a new section named "Package Tests (ptest)" to the migration
section stating that ptest is built but not installed by default.
I also added some cross-reference links to a usage section and to
the ptest.bbclass section.
(From yocto-docs rev: f752867265a1299b1d2790ae59a990a7991a6108)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Failure occurs during make, not do_compile as I previously
noted.
(From yocto-docs rev: 467ea8aa43fac14e3092a30ae15d1ace7a6558ab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6390]
Edits to the "Debugging Parallel Make Races" section. Changes
originating from trying the procedure.
(From yocto-docs rev: 537f5bd8918450e30ea87465025f0069232cb229)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6390]
This is a section on parallel make race situations. The draft
is the first cut at the section.
(From yocto-docs rev: c225d7fe121270a6f82b9fbffa78c7e3914b113d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was inconsistency on how we refer to a task name throughout
the YP manual set. The proper way is "do_<taskname>". Some
occurrences did not include the "do_" prefix. These have been
fixed.
(From yocto-docs rev: b32821bb0d3e6de7bca68b25c662a023526a10c4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed a view wordings to more accurately describe what was
going on. This was feedback from Paul Eggleton's review.
(From yocto-docs rev: 6152a849c0e26178ce13a29b1f353d1b2912427c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The prefix is used for DocBook 5 Schema. We are using the
4.2 Schema. Having this prefix disabled the permalink titles
XSL template (section.title.xsl) produced permalinks with no
titles. Because I removed it in the section.title.xls file,
I also removed it here for completeness. Note that I don't
think the template is used at this point but I made the change
just in case for the future.
(From yocto-docs rev: 8eca4299d0408c1095bfa8aa7b9f04e246db0c0d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Restoration of some parameters to make sure the TOC
is generated correctly.
(From yocto-docs rev: 0f4c4b526fd0e8c3cce3fc033c660112e5dc517f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The mini-TOC was not being generated for the appendix
sections. I added the xsl:param to add it in.
(From yocto-docs rev: 3c083e697b8b6cc639885da45830ce9c4170b00e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Not having a section was messing up the TOC for the
FAQ in the mega-manual. I added a section.
(From yocto-docs rev: d4a34cb1815e3e12e73e08b5ae7b2027b5f03823)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>