Made some suggestions on how and where to edit the SDK_TITLE
variable.
(From yocto-docs rev: 4a4393e00c7108eefaaeaa3951a75524589bf360)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added more detail to this section.
(From yocto-docs rev: 15beb33eadd03391a1af0c9bad0620cefad2a0e2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided more detail and a cross-reference into the SDK manual
where you can change the title through the variable.
(From yocto-docs rev: 9617fa70caef48328455a02d5260e536fac19c53)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable is the default installation directory for the
Extensible SDK. By default, it is "poky_sdk". You can override
this variable so it needed to be documented. The ideal place to
override it is in the distribution configuration file.
(From yocto-docs rev: 67eca50fa973073ce6e7975ab66b89b9706c25c0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two sections that deal with this topic. One is from the
standpoint of a user using a 3rd party published and installed
extensible SDK ("Applying Updates to an Installed Extensible SDK").
The other is from the standpoint of a person providing Extensible
SDKs for consumption ("Providing Updates to the Extensible SDK
After Installation"). These sections needed some closer examination
regarding fully describing what was going on. I provided some
re-writes to both.
(From yocto-docs rev: 1c60b13b5f1813d6e3688e1efce32b7f31422e86)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The title for the section on how to effect changes to an installed
extensible SDK is better suited as "Providing Updates to the
Extensible SDK AFter Installation."
(From yocto-docs rev: 2120ba194abada1769be28ae2737ac12a16adebc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In "Providing Updates After Installing the Extensible SDK" section,
Step 1 had a bit of a grammar error. Not technically, but it
could have been written better. I fixed that.
(From yocto-docs rev: 20f1cad5a813697afd99837699bf52a6586893bb)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added more information on how this is done. Still could use a bit
of detail on how you actually do it.
(From yocto-docs rev: 007bbe40fd11a5f880adf7ad8137d1535f08c815)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I provided some real detail on this variable. It was woefully brief.
(From yocto-docs rev: 4282fabddc81bf4c0fbd0a641ec4f1e9754660c2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a cross-reference to the "DISTRO_NAME" variable as it is
the long version of the distribution name.
(From yocto-docs rev: bb5638409faadb9c6a5fbca729e4e6b8a220433d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated this section with clearer text.
(From yocto-docs rev: 433388ff37297d905c465a5f05d93953dfe062c5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made improvements to this section and tied the variables together
for the explanation.
(From yocto-docs rev: de882b81ed8525dee5e10f247cc6f5c8f15e0f72)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Wording did not match that of similar SDK variables.
(From yocto-docs rev: 696eb9ff0b89222dc696adc0bd28247c0a0c731a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Put in a cross-reference to the section in the sdk-manual where it
talks about customizing the configuration of the extensible SDK.
(From yocto-docs rev: 062db19dd56cc1827ebd7614eb8a54660421df62)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added information on the class in which the default is set. Also,
put in a reference for more information on customizing the
extensible SDK configuration.
(From yocto-docs rev: a0145996aeac1bb45fea9f613789b00327f92d1e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enhanced this description by indicating the class that it is set in
and by including a pointer back into the sdk-manual where filters
are described for extending the extensible SDK.
(From yocto-docs rev: 355b05366aadc337ec3337c0a3c918a23027923b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more detail including the class that sets the default variables
for exclusion and the list of actual variables that are excluded by
default.
(From yocto-docs rev: f24287851998d554575c6aaf9dcc50d198931e48)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This figure had changed. I updated the file and folder hierarchy.
Also fixed some wording.
(From yocto-docs rev: 359292397781f9f5eac2fb693d89ec286ddf9940)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure was incorrect for the installed file and folder hierarchy
for a standard SDK. I updated it. This figure goes in both the sdk-manual
and the mega-manual.
(From yocto-docs rev: a0dc11ce74bba0a18f385d9800f93524340ed033)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Verified a good example and updated the text to match that example.
(From yocto-docs rev: 053467557ef22ce37762222a2997ff9c10be87e8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The value of SDKMACHINE must match the architecture of the machine
on which the SDK installer is being built if you are building an
installer for an extensible SDK. I added a note to this effect.
(From yocto-docs rev: ffdd9a9d00cccf270b5aa236279e6eeea0ff47ed)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the example to more current information.
(From yocto-docs rev: 6952824473f820cbe6d02cba9523c023652f68e3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
FIXES [YOCTO #12734]
Added a new variable description and created a new
section in the dev-manual.
(From yocto-docs rev: 854e641482171585c96ee5b9387b3e64146072b9)
Signed-off-by: Kristi Rifenbark <kristi@buzzcollectivemarketing.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated some links. Also, rewrote the note about the libraries.
It was inaccurate.
(From yocto-docs rev: a0fce0ed36f3d0668e2d211433e7d93fb8833319)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I corrected some wrong information. Provided the correct terminology
for the build host, and provided quotations for supplied values to
be in line with manual writing conventions.
(From yocto-docs rev: 420a7e96e7145dbef31d706cd257059619f71e12)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made several formatting changes for selections. These should
be using quotes and not being formatted in Courier.
(From yocto-docs rev: ec0a2d7e3cfd78fa4e508d5672f1c8265a3600a4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rendered a menu correctly instead of in formatting mode.
(From yocto-docs rev: 7c7da68171dfee037d02fa683c5cba047237fd52)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The step that describes how Eclipse runs the Autotools is too
detailed and can run into problems as Autotools workflow changes.
I made it more general.
(From yocto-docs rev: 5d378a48f7237c620b7fc781b43ee86ea7522432)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to render fields and items from the dialog in normal
text, not in formatted text.
(From yocto-docs rev: 204750e3e2a2e777207d5f2044e38d5482254c46)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Both Neon and Oxygen needed some changes for correct use of the
way we refer to menus and fields.
(From yocto-docs rev: 1cb20243194e61b925df6b0a3b136233f1da8a57)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Used correct formatting for menu items and items fromt the
dialog screens.
(From yocto-docs rev: 9f9d4d65036dc23d193961efb4ae3f236fc8935c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list in the "Configuring the Neon Eclipse Yocto Plug-In
section should be an ordered list and not a bulleted list.
(From yocto-docs rev: 87926b1fb62f3678bd328af3f018f1b17a982092)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I provided similar wordings in places in this section as were provided
in the parallel "oxygen" section.
(From yocto-docs rev: f4fd33d10363ab84f1f76d3e4bf115df45aef77c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to consolidate a couple steps here. When you add in the
location for the YP Plug-in, it auto-populates the options.
Updated the prose to reflect that.
(From yocto-docs rev: b16963844cd573e5f52289f8948b38a5d4a0f7f1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
