Some formatting to fix up Kevin's patch. One thing important was
that the <ulink> line cannot span multiple lines. I fixed this.
When they span multiple lines, the sed script used to convert the
links for the mega-manual breaks.
(From yocto-docs rev: e31012878c709eccae94734f7933559cb1187c47)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch from Kevin that adds a new class. Note that the
patch removed the existing src_distribute_local.bbclass
class.
(From yocto-docs rev: 4ce602093bc9ddfcbcd9392bcc8fd6187885bdf1)
Signed-off-by: Kevin Strasser <kevin.strasser@linux.intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note in the bsp-guide to point back to the main
new section, which is in the dev-manual.
Made some small edits to the main section in the dev-manual.
(From yocto-docs rev: 4105c8edbdc531b2a941d7f7282325fae763f059)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied some minor fixes to this area as directed by
Paul Eggleton. This represents a clean second draft that
can be reviewed. ]
(From yocto-docs rev: d3380d698d36e83aab16ac74e713ab03baef60b0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a cross-reference to the "How to Submit a Change"
section. I added a bit of text to note that the ready can
go there to find out who maintains code.
(From yocto-docs rev: 30a2602c4c0945f1c9bd2a7fa71c1b98e790b2eb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Tracking Bugs" section mentions how to enter a bug using
Bugzilla. I added a new step just before the step that says
to submit the bug that tells the user to be sure to copy the
correct people. The link goes to the section that describes
how to figure out who is responsible for code.
(From yocto-docs rev: 64e58402490267a339c9bade969850da50f39cf1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided three ways to dig out the information on who might
be contaced about a change or patch to an area of code:
1. See the "maintenance.inc" file.
2. Examine BSP README files or the MAINTAINERS file (for BSP)
3. Use the 'git shortlog -- <filename> command to see who
has committed the bulk of the changes for a particular file.
(From yocto-docs rev: 0757a2edddb55bcce2ea1507501220c3097f0a22)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton provided quite a series of patches that I previously
applied. These changes represent the edits from an interactive
review he conducted with me. The series of changes represents
his review for the entire set of changes in the original patch
series.
(From yocto-docs rev: e26f615a01de2b101e97eb6fd7175b813f74295e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Performed some spelling checks against the files associated
with a large number of patches sent by Paul Eggleton.
(From yocto-docs rev: 8b16924aa1da161271cbfce5410344d94c840fa6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New variables DISTROOVERRIDES and MACHINEOVERRIDES resulted in
needing a couple links from the "Mirgration" chapter.
(From yocto-docs rev: cd1b7f7c430eddd5953dc1dac1defe968cfde0aa)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Took out the clause in the parantheses set and replaced
with better structure.
* Ensure we mention what kind of files go into T
* We're talking about recipes here, not packages
(From yocto-docs rev: 8783bb7beb10e0fdfca22648f1dff4a85b760cd7)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that BB_SIGNATURE_HANDLER is OEBasicHash in OE-Core (which has
already reflected in this section) this statement makes no sense, so
drop it.
Changed "metadata" to "Metadata" for consistency across the
manual.
(From yocto-docs rev: 7bdf37f4930a96402344a9b988aee1012b602a77)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable must be set to 1 in order to inhibit stripping, so specify
this.
(From yocto-docs rev: 35c4a025b68857495f252b35bb50288e308dc5c3)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The existing definition was sparse and not quite correct.
I did some rewriting for active voice and present tense.
(From yocto-docs rev: da1eb14573e2050dc03046311d9f2621f5dcc825)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This also necessitated adding HOST_SYS so we can point to it being
matched against by COMPATIBLE_HOST; similarly MACHINEOVERRIDES and
SOC_FAMILY needed to be added for COMPATIBLE_MACHINE (and while we're
at it, let's add DISTROOVERRIDES; however I've drawn the line at
OVERRIDES since that ought to be covered by the BitBake manual).
Quite a bit of rewriting here to clear up some ambiguity created
through article use not specifically associated with subject matter.
Also, some recasting to active voice and present tense.
(From yocto-docs rev: 4090073899e3dfd0e0e6a17aea8210546f08a942)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
