Added the manifest files to the figure and the associated variables.
Also added the test files.
(From yocto-docs rev: cfba55462d1c37ef2ff6454890da64a40f9c3607)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I needed to add some italic formatting for variable type strings.
(From yocto-docs rev: afc6d2d10081f9e9d940075c03b3e704b37cf13b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor rewrites.
(From yocto-docs rev: 71cbc1c389389ffac9e59faacdc56d3ea05facd7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated with a few minor wording changes. Tried to get a little
more active from some of the passive wording.
(From yocto-docs rev: 7dcd8117e3ea40d4b3c1ee5c3b1ea3c2bd29893a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The note about the TAR backend not working was changed to soften
the warning. It has "limited functionality" rather than
"broken".
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
General improvements to both sections.
(From yocto-docs rev: 977fdeaf1258613c3dfc41d78c8125fdba9b2a24)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure for image generation of the BitBake process
needed some enhancing.
(From yocto-docs rev: fc978663a7962d1515d4f47abe8ae522b9e24ce1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The image needed a little bit of clean up.
(From yocto-docs rev: d4fb680be194b7f9b192e06f0081a09504649633)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rewrite included the "do_populate_sysroot" task and a bunch of
STAGING_DIR_* variables.
(From yocto-docs rev: 53484d4982a41f83ac9355aada46526b5d05f64a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
More changes to the "analysis-for-package-splitting.png" figure.
I needed to work in "do_populate_sysroot" task and several
STAGING_DIR_* variables.
(From yocto-docs rev: fcb88024a7dfff1b6cca49770f67bf4c1f548362)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The stage of the BitBake workflow is really "Configuration, Compilation,
and Staging". I updated the title to be such.
(From yocto-docs rev: 4aab6d001119aa8c52e09ef0f6f66694719add29)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable plays a much smaller role since recipe-specific
sysroots were implemented. I have rewritten the description to say
that STAGING_DIR helps construct the recipe-sysroots directory.
(From yocto-docs rev: c1ad18abe67111738efc18725c4f7706b55738cb)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure had the wrong hierarchy for the "image", "recipe-sysroot",
and "recipe-sysroot-native" folders. Moved out a level.
(From yocto-docs rev: e1f45b666b1cd589cee9c9ae6dba01467b991ef9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Figure was out of date.
(From yocto-docs rev: 5b56862ec39fc05299cd6d468f13f75b74c3b800)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a reference to the STAGING_DIR_HOST variable, which is part of the
default directory used as the shared, global-state directory holding
data generated during the packaging process.
(From yocto-docs rev: d68dcec327e96f1da0879681dcde43d4f1769af0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section needed some verbiage tweaks. Nothing major. Just a
few modifications to help clarify some areas.
(From yocto-docs rev: 9deabf424387fd1441882ce8cf28ea69421ea237)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "configuration-compile-autoreconfig.png" figure was badly
out of date. It was not showing the two sysroot directories
and did not use the $BPN variable. I have updated the figure
and placed in both the overview-manual/figures area and the
mega-manual/figures area.
(From yocto-docs rev: dba3b2b65f18870229dcb3dbcb8fadc099165894)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Re-oredered the four options to be alphabetical.
(From yocto-docs rev: 7976ee05c935fd6c24abea99f71436003656cc73)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some key references to the patching areas of discussion across
the manual set.
(From yocto-docs rev: f198529b3072a4a03fd368ea307e8e004c46a344)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The file:// protocol is primarily used for digging out patch files that
are local with the metadata (layer). I put a link in the paragraph that
is talking about them to the "Patching" section in the overview-manual.
(From yocto-docs rev: 18a7b4b81d192fb2cfd96763de4cfabd61c3a0ea)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mentioned the role of SRC_URI earlier in the description as it is key.
Replaced "some_recipe" with "some_package" as the emphisis is not on
the recipe at that point in the example.
(From yocto-docs rev: f7f86941fdf866a693386335374f835078db3ddf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added detail for the step one. Clearer.
(From yocto-docs rev: ef95d547180ce53fade7a3764f8d362422472c7a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found this section a bit loosely worded and could result in
confusion to a user ramping up with YP. I have done an extensive
rewrite focusing on exact wordings.
(From yocto-docs rev: af64c07d259e06fb13572fc224636ed240037b57)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added more content to this task description to help describe how
patching is performed and how the task uses the "apply" parameter
that can be provided with the SRC_URI variable.
(From yocto-docs rev: 6717a3326b0005f6a57be4cc026693b7cd9e8d08)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section presents a deep dive into the patching phase of the
build process. I removed the vague "apply=yes" reference and added
more references for the reader to read and learn about patching.
The bit about the SRC_URI parameters (i.e. "apply") is going to be
covered in the do_patch documentation since that is the task that
handles that stuff.
(From yocto-docs rev: 5a2c98543ccc9ed24d16bb9442b674532940c0da)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new feature (task) to the list of available features you
can use with the variable. The "task" feature saves output file
signatures for sstate tasks.
(From yocto-docs rev: 0669580ce40c46f0b5f8204a6b00e11f725a383c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The paragraph at the end of the section about the file
hierarchies is better cast as a note.
(From yocto-docs rev: 4e8a33be61ea1ea5db12fc5fc97832393213fb5d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure had a bad "PN" variable being used in the "S" directory.
This needed to be changed to "BPN".
(From yocto-docs rev: beafc55eb3646ecb96929e44538de952207f0b76)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure was incorrect. Replaced the PN variable with BPN for
the "S" directory.
(From yocto-docs rev: 440edcdae932a83b6c32b51e85d97178a77b4bed)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I scrubbed through this section and provided much better
explanations of the inside workings of BitBake fetching source
with building recipes. During that, I fixed an error where
the PN variable was being used rather than the BPN variable.
(From yocto-docs rev: 5765987259ac46f140e099d8e1da2ab33f006d36)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided a more complete and clear description.
(From yocto-docs rev: 65505debfb82536e7e2d4ff7e5bc14c6af1a7cf6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a link to the BUILD_ARCH variable. The variable is part
of the glossary but for some reason there was no link to it.
I also added a note for a link to the SDK_ARCH variable, which
was described inline. By convention, I do not like to link to
variables inline as the underlining used to indicate a link messes
with with underscore characters that are usually a part of a
varible's name.
(From yocto-docs rev: a2f487141375ee7ce226eece85424e709ddc67a3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed some wordings to accomodate reviewer feedback.
(From yocto-docs rev: 6de69db7ae5bbbe5e6e7f0b5f6b9b1326f3f5f6a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section had a new bullet added for talking about one instance
of Toaster web server to track and capture multiple command-line
builds.
Also, provided better wording surrounding shutting down Toaster.
(From yocto-docs rev: 9dbe242bf90860afabc9ab218992d2b81aaf8896)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This image was out of date.
(From yocto-docs rev: 061f2766217a6a3914c14e7bfcf09e2c03f73165)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure was out of date.
(From yocto-docs rev: ae84cd2a09f81415e22333d179bcd146560b34da)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As suggested in a recent mail thread by Martin Jansa, there are cases in
which QEMU under KVM will crash because of CPU feature incompatibilities
between compiled binaries and the host CPU under which qemu is run.
Although this is hard to fully escape, we should document the issue to
help people work around it. I have taked Martin's suggested patch
and did some rewording for the new section.
(From yocto-docs rev: 6c625fcf631a82529bc58ec8fb0c18dbe13188d2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The step for getting toaster to create the database schema,
default data, and gather the statically-served files changed.
I updated with the proper steps.
(From yocto-docs rev: 2c3f7ac7f9419c32147be860897984d391a0e930)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The links to the DATABASES, SECRET_KEY, and STATIC_ROOT
were bad. They were pointing to old dated software. I updated the
links.
Also, added a couple new sections. One is how to start a
Toaster environment without its web server. The other is how
to start a Toaster environment without a build server.
(From yocto-docs rev: afe2708014600c0a86c649f6533dd1f6317fe742)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This month and date is always jumping around. I decided to add a
variable so that I only need to to update that when a release date
changes.
signed-off by: Scott Rifenark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the layer-input.png and source-input.png figures.
Had to trim them so they were tighter in the figure. Also,
updated some context in the source-input.png figures.
(From yocto-docs rev: cad644af48b0a1cb2baeb8d2649b9aa7ccbdeda5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Metadata, Machine Configuratrion, and Policy Configuration"
section discusses the three types of layers fed into the OpenEmbedded
build system workflow figure. I updated the figures and text
supporting this discussion. The figure had to be moved to the
mega-manual/figures folder also.
(From yocto-docs rev: 39dd671333f7b3df616920aab08e01c926deca1c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No need to escape out quote characters in a .sed file. Also, using
the @ character is cleaner.
(From yocto-docs rev: f87ca83a6faf5b772d719cd03d6fa0a9b21174bb)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was pretty out of date. I have updated many areas
of the text.
(From yocto-docs rev: 640cdc7fb9d4f93c86b907d631e4f90b261d5ea1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bblayers.conf example files were out of date. Updated them.
(From yocto-docs rev: fd5d75604a3ad66e56c421634f349dce3e38f609)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This image was out of date. I updated it.
(From yocto-docs rev: feb287a72201363c43607508d2e8f1da3993f93f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I removed the less than pretty build process figure and swapped
in the more aesthetically pleasing one. Also, am refering to
the figure as the "general workflow figure".
(From yocto-docs rev: 093f1337131bc658d6afd1b56fb3661a76751aad)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
That figure is no longer used in the manual set. The newer,
more aesthetically pleasing one is.
(From yocto-docs rev: 853567672533777aa5d9baa3969d08673a8dd71f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This version of the figure was not as cool looking as the other
version, which is preferred. I have removed it.
(From yocto-docs rev: ed0346b00ee6b47d90efedd1dd69e4a92a42afe9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was really sparse for being in the concepts chapter of
this manual. I added some more text to it.
(From yocto-docs rev: 9369ba5292126957f89f8b96e06bc2492825c54b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the "Metadata (Recipes)" title to simply "Recipes".
It is less confusing since the term "Metadata" is in general recipes,
classes, and configurations. Provdided a few small edits elsewhere
in the section.
(From yocto-docs rev: 566b54f58ca7859bf860f25e433bff4b429c2507)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The term "OpenEmbedded build system" was being introduced with just a
link. Apparently, that is not enough for marketing. I added a
clause with some more information about it.
(From yocto-docs rev: e7a3a581d44e21976c3f6fe19330e19af1ae0773)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section titled "Development Concepts" is really mis-titled.
It is more about the OpenEmbedded Build System. So, I renamed the
section "OpenEmbedded Build System Concepts." There were a couple
links all within the overview-manual. No other place in the YP
doc set linked to that heading.
(From yocto-docs rev: 889eaf3373a80ca0978ee79ecd2ff26aefb9025b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Softened the opening paragraph so it was not introducing any special
terms right off the bat. Renamed the section on the hardware layer
to configuring the build for specific hardware. Put in a link to
"build host" and used that term throughout.
(From yocto-docs rev: a324cb2f9c499dc8d68d1d87265930c308cbebb7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Challenges" section, the bullet item about YP's steep
learning curve referenced the "what I wish I'd Known" and
"Transitioning to a Custom Environment for Systems Development"
docs. I added links to these.
(From yocto-docs rev: 627042de38495f79d512c6b98c46193b1de0db47)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "License Manifest" bullet needed a link to the License
stuff in the dev-manual.
(From yocto-docs rev: 6350d68a6c1c5432fd833930437b4e5fe502033b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bullet "Releases According to a Strict Schedule" bullet
mentions the release cycle. I added a link to that section.
(From yocto-docs rev: c206c31d20aabe657863fc05274e2d533cdf7252)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a link into the concepts area for sstate.
(From yocto-docs rev: ac395452c3a2f34fb9775c77051b526e39fd9b4c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Widely Adopted Across the Industry" bullet item did not
have good links to the YP home page. Added them in.
(From yocto-docs rev: 8695f3e2bcc2a0d37dd8e6b113639628bffdf4b2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The file was stretching beyond the rendered display window such
that part of the Yocto Logo was missing. Also had to place the
updated .PNG file in the mega-manual/figures folder.
(From yocto-docs rev: 5b73c54fcb2c3f60aee2ff7dc19c4aad102aa505)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed wording to be clear about how PACKAGE_ARCH is being set
when based on the Freescale MACHINE_SUBARCH variable.
(From yocto-docs rev: 76c4ad514e44755f1d4dcec61bb0a74c1b77243e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a section on adding a machine layer. Used Altera as an
example. Also, added a section on creating a general layer.
(From yocto-docs rev: fc36f006bd483a5c26d2b79a18431d16ec27dc00)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the section that talks about building an image for multiple
machines, there was a bullet item on managing granular level
packaging. It had an old example that used the "daisy" release
that showed how to share packages and re-use binaries. I replaced
the example with a discussion of Freescale's "fsl-dynamic-packagearch"
class, which does this type of sharing.
(From yocto-docs rev: ddc224d6d1fe172292dfd0a17f743a1e0a4cabe6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The method for accessing the YP Release Notes for YP 2.5 forward
is to go to the "DOWNLOADS" page of the main YP website and then
click on the "RELEASE INFORMATION" button. No longer does a user
need a simple URL. I updated the two spots in manual where this
information existed for accessing Release Notes.
(From yocto-docs rev: 1e171d3add1048fb81c5a05a11c8ddbaf88e0ecd)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ENTITY was used in two places. I have updated those areas to
give the user new instructions to reach the Release Notes. As of
YP 2.5, we do not have a simple URL that can be used for the
Release Notes. The user must go to the "DOWNLOADS" page of the
main YP website and click the "RELEASE INFORMATION" button.
(From yocto-docs rev: 1c7cdd328baad9a317f4f4f9554999d80d1eb24c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the first example in the section telling how to build out
a Wic image. I could not get the example to run so I used Stephano's
output.
(From yocto-docs rev: 6b4595215d6c24e3efb89288a7547f79ca3e59b7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided a link to the YP implementation of Bugzilla. Added a final
paragraph noting the Bugzilla website if you want general information
on Bugzilla.
(From yocto-docs rev: 78c99c8f42edfee377431cacc10b9ccd4b25c4cf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Link was not going to the top of the chapter.
(From yocto-docs rev: 52da20604a54d16645b4bb4e5e9efa748a00d2f5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed redundant link to CFLAGS in the TARGET_CFLAGS variable
description.
Removed redundant link to CPPFLAGS in the TARGET_CPPFLAGS
variable description.
(From yocto-docs rev: aa95485d44f92b831cd111dbc5bf75526d239db4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The wording to two links (one a variable and one a section in a
different manual) was ambiguous. I added phrasing to remove that
issue.
(From yocto-docs rev: 3b70b4287ca8b2583e0ef559125f1531a2bb6a67)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the link to WORKDIR to begin with. Also, removed the
<filename> formatting that was within the example, which is buried
in a <literallayout> tag set. Doing that screws up the formatting.
(From yocto-docs rev: 0d13dabaa13e5426da35b5d8147f51efa349b5bb)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added "class" as a modifier after refering to the "populate_sdk_base"
class.
Removed link to the TMPDIR variable in an in-line example.
(From yocto-docs rev: 7733a4464ba2893a2363f47996f48587a86eaa82)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several redundant links and wordings in this description.
(From yocto-docs rev: bb9dd8ab6ef9cad387cdddada4f2be093551e38a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A migration item had taken the original section for the target of
the link out. I had not changed it.
(From yocto-docs rev: 10cfaee50455bf10450540f1b381d33f9babf985)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two instances where links were going into the kernel-dev manual
but the manual title was not being used in the text. Added it.
(From yocto-docs rev: 1922f8c79d1667db1fc9b5fe57030302469ca09c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link was to a chapter in the existing manual. I do not
include the manual title when that is the case.
(From yocto-docs rev: 1b7c65b4a2dde3f5d069cb5edc75728492639870)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Link was going to TARGET_PREFIX.
(From yocto-docs rev: 424e8ea3168ab2e910919e6f70fc0b16332ca4f7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I replaced the "<" and ">" constructs with the tags
<replaceable> and </replaceable>. This is the preferred formatting
for user-supplied values.
(From yocto-docs rev: 1fc32486483c545671ffb2142b553da75dbe54fe)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the BBMASK variable, a link to Python documentation was
going to a specific 2.6 release. That release was probably the
most recent when the BBMASK variable was initially documented.
Python has many releases now (e.g. 3.6.5). I re-worded the
description to be more generic and sent the user to the general
Python release area. They can pick a release from that URL.
(From yocto-docs rev: 154aedf79625f37997bec18dba933c514072708e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the first link to the BB_DISKMON_WARNINTERVAL variable.
The variable was linked later in the text. No need to link
the output version of the variable... clunky looking.
(From yocto-docs rev: ec6cfc85ba2f1e2fc763b6b7c918a21cec00e203)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed wording so I could reference the proper name of the
LABELS variable.
(From yocto-docs rev: 05e5f287bde8219d1f8125d71fd48a36a422009a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The actual title of the sdk-manual does not include the word
"Manual". So, the reference to the book should terminate with the
word "manual" in lower case.
(From yocto-docs rev: 41bc85776f0b172fc243b6e5a5ca13b72e8399e5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link was just going to the top of the section. I added an ID tag
to the actual host-user-contaminated test within that insane.bbclass
description. Now, the user is linked right to that test.
(From yocto-docs rev: b1e5b5a1876e211a8c57bfa727fa9031cfe5e0ac)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Had the wrong ID in there.
(From yocto-docs rev: 6d52354b42709867ef61543de6d3b630fd780bab)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The focus of the discussion here is on the DEPLOYDIR variable.
Having the link to the variable DEPLOY_DIR adds clutter to it all.
Removed that link.
(From yocto-docs rev: 8561c70fcff88adc82c7c5998d2539d40b314888)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Took out stange parenthetical construct and the links to the B and
S variables. Links were redundant. The construct was weird.
(From yocto-docs rev: 9cd2bf116bd89288a93944359a4809e68fa61f7b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A "naked" reference to the bsp-guide was split across two lines
in the *.xml file. This splitting causes the link to not be
processed correctly by the mega-manual.sed script. I joined the
two lines to fix the link.
(From yocto-docs rev: e31b4d2210b5c246f3e822fbe8950a625e08ca98)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Missing this conventional part of the reference contextual diatribe.
(From yocto-docs rev: 5468ebf21bc9166de35e9b7016eef06ed586e5c3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Trying to get back to a standard of using an actual link for only
the first occurrence of a variable in any given section.
(From yocto-docs rev: 68d80a5dd8481f938892473c4671a9c436e80c8f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the migration section, an older name for the bitbake-user-manual
was being used in the text for a cross-reference. I replaced it
with the current and correct name.
(From yocto-docs rev: 3f466b59a3138984cceae12ac58c84ec3cda4432)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the migration section, an older flavor of the title to the
sdk-manual was being used. This of course was not processed
correctly by the mega-manual.sed script. I fixed the title so
it is now processed correctly.
(From yocto-docs rev: 1f9fa699bb14f96a7c9ccab314a7d72e6a93dda6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The terms.xml chapter had a link to the toaster-manual where the
string to the manual was not matching the string used in the
mega-manual.sed file. Consequently, the link was not being processed
correctly. This type of link should not be a link in the mega-manual
because the target is to the manual in general. Fixed the string
of the toaster-manual to match what is being used in the mega-manual.
(From yocto-docs rev: 44042847db10b15f8694199162ad96dea44d21bc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The areas were found scrubbing the mega-manual. These were minor
fixes.
(From yocto-docs rev: aaa460be3f4a446c091d66a17ca6c010f335ccc4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I was using the "/cgit/cgit.cgi/" string as part of the link to
the source repos, which uses the ENTITY "&YOCTO_GIT_URL;". That
ENTITY is all that is necessary to get the link to work. I removed
the other stuff.
(From yocto-docs rev: f9a63c2cc824ef05230f614e933d178469890e97)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. Fixed the name of the "do_compile" task so that it was not
referenced as "do_compile()".
2. Fixed a link to the Source Repositories so that the link
used the ENTITY for the YP Git area and not a full-blown
hard-coded path.
(From yocto-docs rev: 4b8d0e61f3f3017954d36ed196a08fb0a04909dc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "end" part of "linkend" was missing.
(From yocto-docs rev: 9411033faa6f71a52080c2f35a2af2f725399c7b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a link to the old kernel-manual in the reference manual.
This manual is not used. I changed the link to use the proper
ENTITY value and also removed the old one from poky.ent.
(From yocto-docs rev: f1377989ab4a85827f5aaab9b19c4fb3c10567ca)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a link going to the "kernel-manual" manual, which is no
longer used. Changed to "kernel-dev". This was a fix so that
I was using the proper ENTITY in the poky.ent file.
(From yocto-docs rev: 787ee10c7764ffd6adfbd8ddb304ac686bf3e95f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Link was going to the right place but had an old chapter title
name.
(From yocto-docs rev: 57a5d25180429a97d47678c0782198623bc06eef)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The former is deprecated.
(From yocto-docs rev: 1a1f89d91ceeb35f8cb5c2f9fc42fdb089ffc05c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The location for nightly builds changed to
https://autobuild.yocto.io/pub/nightly/.
I updated the YOCTO_AB_PORT_URL and YOCTO_AB_NIGHTLY_URL
ENTITY variables accordingly
(From yocto-docs rev: 5a80544901ed6f0fd2188e82ac3dab7637d28aa1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found several instances of this being referred to as the
"OpenEmbedded Metadata Index". Changed to "OpenEmbedded Layer
Index".
(From yocto-docs rev: 60fb601be324a350cd4d51b199915e6b72e2f9b0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Had "Toaster Manual" in the cross-reference so it was not resolving
correctly when processed by mega-manual.sed.
(From yocto-docs rev: c99ce4a706df55e97388b45620ed2a503cb8312d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Nobody provided a figure for me for this section, which would
have been nice. So, I have generalized the text to work
without that detail.
(From yocto-docs rev: 7570167196c26c9eb08e97d1350a715bff37c75f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
