The "Configuring the Neon Eclipse IDE" section needed a bit more
information in the note. Telling the users that if some options
are already installed they will not appear in the list.
(From yocto-docs rev: fbee757f102ee51e4db9fb6bdfd516775de8b5e0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Steps indicated you had to be in a clean directory to unpack the
tarball. This is false. You can be in any directory and unpack the
file. Unpacking it puts all the files into a directory named
"eclipse".
(From yocto-docs rev: 3e2fc8d013b51c1a90a44cf32a6cd69e2ef80a22)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed this step to be more accurate.
(From yocto-docs rev: 1a5c25c57a8f5829a8c3302520661def856adb58)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link was pointing to the Chapter 5 as if it were in a different
manual. The link worked but should have been pointing to the actual
section of the Eclipse flow overview. Fixed it.
(From yocto-docs rev: 4cc906bf383af837855f4c40fc107c77ff6d3ff9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Using consistent wording.
(From yocto-docs rev: fad0230d99259aa94ef3d8db30bc81394b8da4ac)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The step describes the installation process and the intial launch
process. No information exists for describing how you launch
Oxygen from outside the install process. I added a note that
tells where the "eclipse" binary is installed and an example
line to invoke it.
(From yocto-docs rev: dc59410caf18e36497d70ea3c877b4f82f620e2c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided better instructions and accounted for the fact that it
is just this workflow here that is assuming the need for a
YP-built image.
(From yocto-docs rev: a05091768c914817ed262b15d39e7c9b54a5b863)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the "Workflow Using Eclipse" section head to not match so
closely the "Working With Eclipse" section heading. TOC appeared
funny.
Also, updated the step 1 to be more accurate regarding the real
need of having a YP build host and where to go to get information
on setting it up.
(From yocto-docs rev: 1cbca098a2f793bd86b6f73d3d35ce79bdf639f0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found several items that were slightly off after working through the
procedure. Updates to bring it into line with reality.
(From yocto-docs rev: 0f34afe3c37dedda28a1a5714703787a5dfe649d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Expanded this section to contain a figure of the flow and an
example that showcases the ways to override and use SDK
environment and Makefile variables.
(From yocto-docs rev: 834c059c1df4e8328248ea86fa23ca9a397351fa)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Makefile-Based Projects section was expanded to add a useful
example and figure. Added this figure to the sdk-manual and
mega-manual figures folders.
Updated the Makefile to include the new figure as part of the
tar files for each manual.
(From yocto-docs rev: 6261cb55b6393e0d5dce91cdb7c8e6e83849ec0c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Autotools is simpler now as it uses "autoreconf" to one-step a bunch
of the existing tools such as aclocal and autoconf. I updated the
figure to reflect the simpler flow and also the steps that accompany
the figure.
(From yocto-docs rev: 380cb1bb89003229befb4715e875586c798d6735)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I wrote the section to include a flow diagram using "make" and
provided a working example highlighting how to override environment
variables.
(From yocto-docs rev: 00e8e09a51a1f0305317f38975a9d7695c92bdb5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two changes here. One was a note to the "make" step of the
Autotools-based section. I cross-referenced the Makefile section
for information on how SDK installation environment variables
are respected and or overridden when using make variables.
Also, fixed the quotation syntax of the four environment variable
examples used in the "Makefile-Based Projects" section.
(From yocto-docs rev: 5bd4e056496ff3478e213ccd9e49adfe1fac67ab)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New figure for the section on Autotools workflow. The figure
goes in the folders for both the sdk-manual and the
mega-manual.
Updated the Makefile to include the new figure in the tarball
when creating both manuals.
(From yocto-docs rev: ccb2c4b9ebd0b0aaa55b5790eb6a916701e10af4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Did a re-write of this section with better explanations.
I also pulled the bit about passing parameters to the
configure script into the step that talks about that.
(From yocto-docs rev: 79432ba0eb0cc2f6bdb3410fbf99f227fb666b2c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The line used to be "AC_PROG_INSTALL". I did some digging and can't
really figure out why the example is not following the standard
"helloworld" stuff out there all over the internet. So, I have the
user create a configure.in file as follows now:
AC_INIT(hello,0.1)
AM_INIT_AUTOMAKE([foreign])
AC_PROG_CC
AC_CONFIG_FILES(makefile)
AC_OUTPUT
The original was as follows:
AC_INIT(HELLO,0.1)
AM_INIT_AUTOMAKE([foreign])
AC_PROG_CC
AC_PROG_INSTALL
AC_OUTPUT(Makefile)
(From yocto-docs rev: ed86d61178f86df3248b34d52602121c39bd56b5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link was going to a spot from which another link was suggested.
Too many redirections for the reader. Linked to the original place
instead.
(From yocto-docs rev: 9fc383a99ae0a7ff8cae761c0c31b27030f765cf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Formatting used for the "configure" script created using the
"autoconf" command in the example.
(From yocto-docs rev: dd55ceb2c19f9e013c13e776acf7201c25501ff7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Autotools example called for a "configure.in" file as part
of the "hello-world" example. When working through the example,
a warning occurs saying that the file needs to be "configure.ac".
I changed the example.
(From yocto-docs rev: 7f677e3bbf0331228ed5aed1ace7c55d523d3121)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to reference a couple terms for first use: "cross-development
toolchain" and "OpenEmbedded build system".
(From yocto-docs rev: 2370c3508574efe05e768f4515fec5b17f0ca177)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor edits to this section.
(From yocto-docs rev: 68a6e4cac6cecd14e87d4f05f558d79165761d4d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the output to reflect the real command's output. Updated
prose to match (mostly) that used in the similar extensible SDK
sections.
(From yocto-docs rev: fb6c8895f2afda0c43bbaa49870c425e25841ec4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed some poor writing in this section.
(From yocto-docs rev: 5709c2c2c1c37166ec5df1193b58ff82bb10b4c3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor edits.
(From yocto-docs rev: 3ed2c1026bf03feb03001e00daec55b94d7dc35b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed a grammar error and made a few other corrections.
(From yocto-docs rev: 369a22ffe3780fd00514344f1b3b8a944305e320)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a cross-reference to the term "build host". Corrected
a subject/verb grammar error.
(From yocto-docs rev: 8763e333867d0039315f0ca0aa96fdadea676783)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was poorly organized with a mile long sentence as
the opener. Fixed it.
(From yocto-docs rev: c7624244e40c807d1c3cea80d2eced3cd9948019)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed a few sentences up by providing clearer text.
(From yocto-docs rev: e81984d73c05f2d722bc082a100d01c3cc0173ab)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a cross-reference link to the term "bulid host" and removed
the redundant word "system".
(From yocto-docs rev: 205d6fb6030cecb02301ec9cdc92ac908d250160)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed some prose in various places.
(From yocto-docs rev: f754969eff4c314d9f4c489cca2b3c2f8fd87fff)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updates to prose for better understanding.
(From yocto-docs rev: 44a07560845c973a0da4c27969c740d3d712d323)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated various prose for better understanding.
(From yocto-docs rev: ddbd66d7732bbc8b4940c660f8a8c941a5cc4ea2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poor writing left over in here. Updated some of the prose.
(From yocto-docs rev: 8f71cd997c86610dd62780f74f39dad811098540)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Corrected some prose to be clearer.
(From yocto-docs rev: c73f3d486fab555e6c6ac3dd1f5fbaf4d531ab29)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Took out the $TMPDIR part for the output and left more generically
as "Build Output".
(From yocto-docs rev: 4b0375e3293d67e4b5be433cd6c468532fee5a30)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Edits to improve this section.
(From yocto-docs rev: f062882b3b3cf9c454466fa9d243284d97592bdc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more detail at the top for how the local recipe interacts
with the Upstream Source.
(From yocto-docs rev: c1d49a7c00c458b55396c0efc7a329acd870be6c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor edits from the read-through.
(From yocto-docs rev: d165438d3d02f3154fc59197d75ab1cb6a285320)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more detail on how the upstream source or files from
srctree are located.
(From yocto-docs rev: 5eff4b1b68c232071814969b6367188352639f17)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Had to update the figure to use "Upstream Source" labels and
fix a wrong "devtool edit-recipe" command. That new figure went into
both figures folders for the sdk-manual and mega-manual areas.
Provideds some cleaner wording.
(From yocto-docs rev: 6225d04dd0551a840d929b752225064a222962bc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the way we handle the list of exported variables resulting
from running the *.sh installation script. Rather than list them
all out (they were getting to be quite numerous), I am referencing a
few as examples and recommending the user look at the actual *.sh file
if they would like to examine the entire list.
(From yocto-docs rev: ce2c1491f4f0991cad5f8d4a220a102adb024624)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some Minor edits to this section. Also, a scrub of the list of variables
exported when running the install script. The list is out of date and
is missing many variables. I noted these in comments for now and will
add them in later.
(From yocto-docs rev: 739a2ca42ee798625492ddb51a32ad09f80aa960)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The text had not been updated to include the many architectures
now supported in the Index of Releases toolchain directories.
I added the list of architectures.
Renamed the section to a more appropriate section heading.
Verified the example and put in the latest output.
(From yocto-docs rev: a567f5101d230ef1fa4428e9c6905e9e23bd5855)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #12628]
The syntax for MACHINE_EXTRA_RRECOMMENDS was off in the machine.conf
example. I have removed that leading space, which should not have
been there. This matches the actual file in poky now.
(From yocto-docs rev: 11e38c4c2b23f9a8ae9a0655a07af1a5682c24b8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This chapter only had the stuff about submitting a defect against
YP and making a change to YP. I moved that information into the
common tasks chapter as it is "how-to" information. Removal of this
chapter alse required that the mega-manual.xml file be updated to
not include the chapter.
(From yocto-docs rev: 4421b1585c21a6f7862525ba972f7e765626066e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Renamed to "Speeding Up a Build" and moved out of the setting up
chapter to the common tasks chapter. Fixed a couple links in the
ref-manual.
(From yocto-docs rev: c53fddd353230c8ef1abc21c7a2d2b1f492f034a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section is now organized under the parent "Building" section in
the common tasks chapter.
(From yocto-docs rev: bc1bc9965cda547e45ff09a1c9e77be5e8c0a3d9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section is now organized inside the parent "Building" section
in the common tasks chapter.
(From yocto-docs rev: 71be83e1ebfd2ad8606bddf852a4c06ab7d7c53d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section is now part of the building parent section. I have moved
it there in the common tasks chapter.
(From yocto-docs rev: a9fccb1bca8e18169d93416c7a6e17723bcf01c7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section now belongs under the parent "building" section in the
common tasks chapter.
(From yocto-docs rev: dad6029b9b45fd6ec564894ba101991fd8a2162e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a "building" topic. I moved it beneath the new parent
"building" section.
(From yocto-docs rev: 0426f0dd6871c8063476945b93743ffc5cfc0856)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had a section on building an image up in chapter that talks about
getting set up to use YP. I moved the build section to a new parent
section that will hold topics on building various things. I renamed
the section to "Building a Simple Image". I had to fix several links
in the sdk-manual, overview-manual, and dev-manual.
(From yocto-docs rev: c119fc7c6148e7b08acad374fe2981842e9462a3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed to "Locating Yocto Project Source Files". I am moving the
sections on cloning repositories out from under this section.
(From yocto-docs rev: 3889aadab9b603097b6cc5b7afb9d0066021106c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Setting Up the Development Host to Use the Yocto Project" title
changed to "Preparing the Build Host". Fixed links in a lot of
other manual.
(From yocto-docs rev: 00e487e01a0e2a16f5b8d786b3124cbe5115b38b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was in the chapter on the open source development
environment. It is better suited to be in a newly named chapter
"Setting Up to Use the Yocto Project". I have moved it.
(From yocto-docs rev: 028f8f7a1b93a023a99ffadb01b0da699b4081c2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The chapter was not the best given the new nature of the manual. I added
better introductory wording.
(From yocto-docs rev: cb4695575c0105e0cd5e50c2132e98553babe147)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on licensing in the overview-manual was really "how-to"
information. I moved this to a new section in the dev-manual for
"working with licenses". I fixed some references in the ref-manual and
in the bsp-guide as well.
(From yocto-docs rev: f150a1ea2da900aae88fc5fa60f4115cc213ba2d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #12517]
Added some qualifying information for how to generate a list of tap
devices to enable runtime tests on QEMU.
(From yocto-docs rev: 4359a355944f6cf4ec1e14ecbedc690ef37ff743)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Wayland and Weston topic moved from the overview-manual to
the dev-manual. The topic was really a "how-to" topic and not
a concepts topic.
(From yocto-docs rev: b0f20a67c99590c48d595f4e572339bb5b6b83b3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Wayland and Weston topic moved from the overview-manual to the
dev-manual. The lone link to this topic was in the ref-images
chapter. I updated the link.
(From yocto-docs rev: 6c335f8d3618e3285f91fe20aea33a1c1f1c0ddf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two sections at the end of the shared state concepts section
in the overview-manual are really task sections. I took those
and created a couple new sections in the dev-manual to house
those topics.
(From yocto-docs rev: 86382e7873d796f44554c8e04d3bd8091d350f51)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed "OpenEmbedded" in the string "OpenEmbedded build system."
(From yocto-docs rev: d44b370b0fb993c32c9dfe3515188fa9e7ff2437)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the line with "stamp-extra-info" flag to the example from
the deploy.bbclass. This line was missing or it had been added
since the original writing of this section.
(From yocto-docs rev: 50f5482c2132235962d4ab48d0d7263628df1728)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made some small edits to this section.
(From yocto-docs rev: a2cc355c1bdfbf10f86f8d4994cc81dfb12d8f87)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that 2.5 has released, I replaced the ENTITY variable used for
the moving month and year with the actual release month and year
(i.e. May 2018).
(From yocto-docs rev: 2d6e8ddce4fce0c405d2aea69cea2a5b262410f7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more realistic information on how this variable is set.
(From yocto-docs rev: 47e6cb7d00eeb8001c4a53c13600feb5ef4d4660)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the descriptions for the SDK_HOST_MANIFEST and
SDK_TARGET_MANIFEST variables.
(From yocto-docs rev: 212d6c5b3290016431604e67dfb27a1408ac0463)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
