I added a link to the PRSERV_HOST variable. That variable is
now defined in the ref-manual variable glossary.
(From yocto-docs rev: 7166fe94107cd379081fd81b7351ec081aa2c6ae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Forgot the part about the class being automatically enabled
when using the Hob.
(From yocto-docs rev: e15b52fc703f2bc4c02e2afe05de1cc4d057b685)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previously, we were documenting the "package*" class and lumping
the "package_deb", "package_rpm", and "package_ipk" classes in
that entry. Really, we need to break out the "package" class on
its own and create entries for the sub-classes that were being
bundled in there. Additionally, we needed to document the
"package_tar" class.
(From yocto-docs rev: 608edf7eaa264d5e20c6ffb5d2a6173d38b42ebc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Noticed that this class file name is "image_types.bbclass" and not
"image-types.bbclass". Fixed it.
(From yocto-docs rev: 594cc933c919b7b84248c670ed7563bd23b8597d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note to the existing IMAGE_FSTYPES variable based on
using "live" as an image type. Need to be sure that appears
before inherit line in the recipe.
(From yocto-docs rev: 1fc45b2bc7c70f00882d495d659830b94eb7d2df)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I accidently removed this so had to add it back in.
(From yocto-docs rev: 928bc686735fb8bc80df2a8c070846c33ca6aa3c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Told where to set this variable.
(From yocto-docs rev: f95fb5821383721da6a63bb8eb74807e89e6b21d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created glossary entries for the GRUB_GFXSERIAL, LABELS,
APPEND, GRUB_OPTS, and GRUB_TIMEOUT variables.
(From yocto-docs rev: 31bcc25866525ef998bc01e11ab9ddb0601b8ded)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I put this name in wrong in the original commit.
(From yocto-docs rev: 654ba14a17886b5743e6732f825a693375d264cf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The entries for gtk-icon-cache and mime are placeholders only
with this commit.
(From yocto-docs rev: 8652cc5d4fe880768e746a80dde82513c5d83a09)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to the way in which IMAGE_FSTYPES is processed, it is not possible to
modify it using _append or _prepend. Therefore add a note to the manual to
warn users in case they stumble on this issue.
(From yocto-docs rev: 164aee65a6796ccc24c2734bb7440a8d6531f180)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As an actual example of using AUTOREV, refer the reader to the
Yocto-supplied poky-bleeding distribution.
Also cleaned up some wording and added a Caution statement
about the distro not being regularly tested - Scott
(From yocto-docs rev: 2a74573af702c905274e377304a946fd335a0182)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
i'm still looking at the dev manual for more changes but those would
be more substantive changes, so i'll pass along just this collection
of minor stuff.
(From yocto-docs rev: 94e2422d6e6e408e2dd76b15e1231814b123800d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This now involves only making sure that "packag-management" is not
part of your IMAGE_FEATURES statement for the image.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 9cb66c40677adc43088d22900fef58166ee8b508)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the intro text for this one-line example so that it
would not imply that the example is the only syntax that can
get the job done.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 5d0151b692bef9ef67a6237f3e4e4387e6f00c63)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a small note in the section where you create your own
distribution to be clear about where the name is set.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a2ce7d82eb7f3edbaebce65c73e6ae3c0c921152)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rather than saying menuconfig is "built", I changed the text to say
it is "run."
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 74b7a193e8356931e5a0db2ea76b4543880ed2ec)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The four sub-sections describing how to customize an image seemed
to be backwards as they progressed from most complex to easiest.
I switched up the order and provided better transitional
introductory wording for the four sub-sections.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 1e8d178c401d3020621fc90af5cdd0bb3e37be87)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I applied some review edits to the USERADD_PACKAGES and
USERADD_PARAM variables from Paul. Additionally, I added descriptions
for the GROUPADD_PARAM and GROUPMEMS_PARAM variables.
(From yocto-docs rev: 0c52a79efb2cf7c708ea989ab307be04f27484dc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 4eb9a5c6df085e57e7885e12fdbdcc85f61c101d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 6ace08dcbaa08fd13d4d8f49d34dd90240e65761)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This needed some work to be more descriptive.
(From yocto-docs rev: 2ea324c84f5aaaf3c30d1c71396fa3d5372669a0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Took care of some quoting for the "x11" feature and also a
messed up sentence in the second paragraph.
(From yocto-docs rev: ed71135edbdd8de02cbb6d7cc972aab0e269e4cb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I noticed that chapter 10 of the ref-manual still had
"Reference: Features" as the title. This is left over from way
back. I changed that chapter title to "Features." Next, I
noticed an inconsistency with some sub-section titles.
I changed the "Images" title into "Image Features." This affected
several links across the doc set so I had to update those
cross-references as well so they have the latest section title
as part of the reference.
(From yocto-docs rev: b68f009a92e0e24802e367d98cf66e15ba1cd364)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: bd9f4ab6bd54a6d0edff1f5cfb6ea4d46f5bc9f1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Dependency Graphs" section, the pn-buildlist file was
not mentioned as a file generated by the
'bitbake -g <target>' command. I added this in and provided a
bit of re-writing.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 435de6a980bd182e8033319e479ded1414e93eed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This term should always reference a users current working directory
and not be confused with the OpenEmbedded build system's "work
directory (WORKDIR). I found several instances where the term
"working directory" was not used correctly and fixed them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 300c78c1d54b2a4fbb8ecca03faa7c8c67bdc54f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed extra "the"
(From yocto-docs rev: 58582739dcb3f969ee44b074040bb64773d9d4bd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the MACHINE_FEATURES, DISTRO_FEATURES, and
COMBINED_FEATURES variable descriptions to better reflect what
they actually do. Also, fixed two occurences of IrDA in the
features lists section.
(From yocto-docs rev: af79b0b3bc88ca0811d488c7c5d6b5407de808a7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Very rough draft for this new variable. It will likely
change.
(From yocto-docs rev: b535542975ae469753cb27ce59f9f716167384fb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The operator used was "=" which was inconsistent in light of
previous uses of the variable in the ptest section. I changed the
operator to "+=" to be consistent.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: d6b7c7e15290e64f4baac25544224788e92ad309)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After adding "Package Group" definition as the original "Task"
definition, we needed to create a new definition for the term
"Task".
(From yocto-docs rev: b6eae9242bf488d3f086e496b52d8422ad31feb6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: faa7206b2f67a26c1366fe997cd092aed7e9f85e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the note indicating that three specific recipes were
"ptest-enabled" for the release. I substituted in wording that
tells the user to see if a a recipe inherits ptest as a way
of determining if the receipe is ptest-enabled.
(From yocto-docs rev: 9136617575eb7a0a08f0b81f75ae6cdede62219f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The image core-image-gtk-directfb really should be
core-image-directfb. Also, we need to add the core-image-weston
image to the list of images chapter.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 66625cc8da339d3096edbc8623ca4b91b4bb6858)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the wording so that it reflects better what is actually
going on when use IMAGE_INSTALL to afect an image.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 243588460fb76a0c333772e3dce566cf664397ee)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added glossary definitions for BUGTRACKER and
CLASSOVERRIDE.
(From yocto-docs rev: 79c10f1cf0f18429eb41b035ed60264b48549e9a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The BB_DANGLINGAPPENDS_WARNONLY variable seems to be able
to be set using "1", "yes", and "true". And, it is set using
these various methods throughout the poky metadata. I guess it
has caused a bit of confusion so I have added the fact to the
description.
Reporte-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 651e09aba67f9d62ce005529f16a776c0ab593f1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If someone wants to check this over, make sure I didn't make
any silly changes.
(From yocto-docs rev: 3305553d84fbd09fb00d4608533f830348fda0cc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Given the length of the tools sections in the profiling manual,
I'm doing each tool separately so that patches come in
manageable chunks.
(From yocto-docs rev: f6544c8df852f83619d942b3a6f624fc62981a40)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
given the length of chapter 5 in the dev manual, i'm going to do
this in bite-size pieces.
(From yocto-docs rev: ccfe3e719bf71236e50b3e4507a6d63199f24ff5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* is it technically correct to say there are now 5 BSPs? as in, does
genericx86-64 count as a new BSP distinct from genericx86? [aside: are
there any plans for a MIPS64 BSP?] - rpjday
MIPS64 is under development. - scottrif
* if scott is up for it, a couple more variables for the variable
glossary might be BASE_WORKDIR and TARGET_VENDOR, which i would have
added to that variable list but they don't appear in the glossary
- rpjday
Noted. - scottrif
(From yocto-docs rev: fae6f8baebedaa72f5e37b4f1a39a9accf9b196c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
scott (or anyone else) is welcome to use any or all of this, or
tweak to taste. i have a few other concerns with ch 2 but i'll read it
more carefully to make sure i'm reading it correctly. - rpjday
I implemented all but the addition of MIPS64 as it is not tested
using the autobuilder yet. - scottrif
(From yocto-docs rev: 927ff9be66a7471a33faf18a1122ce8b2bd21805)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The examples went stale. Two out of three did not work. I have
provided new examples that work.
Reporte-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0a3695f3f6a5b31617f4a5da960677f87733b825)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed wording to remove implications of meta-intel clone
importance regarding working with BSPs.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: e5f80aadf6f651af6efae6e99d0a4d9b6e76fc99)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't even support these Linux distributions. We should not
have a FAQ entry telling people how to deal with it. If the
distro is that "hot", we should take steps to support it.
(From yocto-docs rev: b2f77f048da82becb590f948c41e94598817b4ee)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I re-wrote this FAQ entry to indicate more recent versions of
Python and to leverage off the way we can now download or build
out the buildtools.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: a4743936fa6dcd9449f0def771d116c53db7aa7e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was inconsistent use of the way directory names were
handled throughout the YP documentation. I have scrubbed the
set and replaced many instances such as the following:
meta/<something> replaces /meta/<something>
poky replaces ~/poky (except in some very specific examples)
I basically got rid of leading slash characters.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: ae2e451ed8f61484d04b30017021912c4493a441)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Significant tweaks:
* removal of (confusing) leading slashes from YP filenames
* deletion of reference to non-existent "build/tmp/pkgdata/"
(From yocto-docs rev: c105ae9c6741fbe195addf52d313925bab50ba40)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This folder disappeared and I was not told about it.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: d2526d773d282cf81e81f60745a47fbdc9625254)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more wording to clearly state what is going on when you
run this script.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 2b23966d80b2787f7eddcbf6c635220d58d7a494)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I altered three areas from the previous patch submitted and
applied from Robert P. J. Day. Two minor wording changes and
removal of negative language.
(From yocto-docs rev: 0212b01f82637c3498f26bce57e98508c84799c5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert P. J. Day noted that the bitbake command no longer uses
a wrapper as the section indicated. I have removed this reference.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a523d4d4fc57edabfa4aa7d20e154cdc43d35fca)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was some confusion over some things in these two sections.
I re-wrote them with the help of Paul Eggleton to be clear on
them.
Reported-by: Robert P. J. Day (rpjday@crashcourse.ca>
(From yocto-docs rev: ab352523e82626d8356d8b2c07fb10d2d60ea254)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Investigating this section for an apparent typo it was decided
that the term needed removed. During the process I re-wrote
the section for clarity.
(From yocto-docs rev: 0ba7e364a49328a2cd57f67ed1a540bfeffc9e08)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
Some edits to remove a link to the YP Metadata definition.
The metadata referred to here is for opkg only.
(From yocto-docs rev: 777969fb3b74e638fedb638d161e2f92ac0a5f4c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
Added a cross-reference link for this variable into the glossary.
(From yocto-docs rev: a6f4935b60222a97a5fe03a538a3f8042e18d3f6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
As part of the fix for this bug, I have added a description of this
variable to the glossary.
(From yocto-docs rev: ad988c82b364bb0c629bcb2ce04f99e0e371622e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three chunks attempted in a patch from Robert. Two out of
three worked. One did not because the text had changed due
to re-writing a note that had some links to out-of-date
wiki pages.
(From yocto-docs rev: 7f807d6df4842d47534c4011ccf67fd01bf0b830)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch from Robert P. J. Day. Good catches for some minor
wordings and such.
(From yocto-docs rev: 44c98e879bddfee49a5b89e7bb9c94c403284140)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch applied from Robert P. J. Day that basically amounted to
a good review of this section. Robert caught several typos and
small writing issues throughout the section.
(From yocto-docs rev: e44bb5897dbcc7e96bfbc730f6abe87cc2df2f3f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
The developer's manual should only refer to functionality which
is available in oe-core. Currently, this passage requires the
user to add a package from, and use facilities of, meta-oe. This
fix describes how to use facilities in oe-core to the same end.
(From yocto-docs rev: 2dfaa88ae4760f86dbbdc8b58de7feba25a8014a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two links in the section discussing Linux distro requirements to
wiki pages were terribly out of date. I have rewritten the note
to remove them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 918e2e9d1146e828a2bbd16d8f5bad837effe088)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The links to the supplemental information wiki pages on setting up
your system to run YP were terribly out of date. I re-wrote the
section to remove them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0a2a2b95781e6b70d584612c33f81839cf7a10c1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The formatting for the "Caution" boxes was poor. There was no
apparent reason in the style guide why these types of admonitions
should appear any different than "Notes" or "Tips", which look
fine. I could not devise a .css solution so I tricked the
formatting by using the <title></title> tags in combination with
a <note></note> pair. Basically dumped the <caution></caution>
tag pair. It looks okay now.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a53d6f0b3a22cfd87f841c03452b5ebce2b1b474)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5440]
Needed to add this to Ubuntu and Debian as an essential package.
Updated the variable so that both the QS and ref-manual will
have the package listed.
(From yocto-docs rev: 3b5b198c971af12cfe395c3828e01f7fb369e7a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The etcdir string was replaced by sysconfdir.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 095a9226171189f17c0671b05196cef58da33732)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable is only used when building an image using Hob.
The description implied otherwise. I clearly state this now.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 12b671aec1df367c107d906bbefb44da56b2adec)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5203]
This was reviewed by Alex and an ordering change was needed due
to the order of how things are created during the workflow.
(From yocto-docs rev: 0c630fed9f9a609c1ca13359efe47cad6f60e00b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Documentation fix for [YOCTO #5347]
SDK created useing the "-c populate_sdk" will not support static
binary build without proper staticdev library packages.
I have added a note to inform the user about this limitation.
(From yocto-docs rev: 91409d77d68e55f4089cab3e7f48dd385dddff2e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial fix for [YOCTO #4414]
I put in the API stuff as well as made sure the other comments
for the dora-toaster branch and temporariness of the GUI were
mentioned. Probably more tweaks before this section settles
out.
(From yocto-docs rev: 4df966bb21a014b8fcac69abb7b912e109089606)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial fix for [YOCTO #4414]
Got some feedback on the section and added a step that the user
needs to checkout the dora-toaster branch after clonine poky.
Also, that the Django version is specific and not the listed
version +. Finally, a bit of wording to note that the GUI is
temporary for this release.
(From yocto-docs rev: 775d55f33a4dfbb21db896b81159e16ee7e16034)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial fix for [YOCTO #5368]
The list that summarized where to get YP release did not include
the source repositories. It basically just listed tarball
areas. Now that cloning the Git repo of poky is the preferred
method for obtaining YP, I made sure that this area was the
first spot listed and called out as the preferred method.
(From yocto-docs rev: d5aabd2cb70ea7b7caf5f39d0630ba6961280e1a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link had a hard-coded 1.5 in it. I replaced it with a
&DISTRO variable that resolves to the release.
(From yocto-docs rev: ce7ae7131a7e1d79bbc67e82cb5232a6ffbaa324)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-yocto-bsp/conf/layer.conf example had gone stale.
I updated it.
(From yocto-docs rev: bf77d70789f85400e2d6be7e4e32475506183217)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This site has disappeared and I don't think there is a
replacement.
(From yocto-docs rev: 711488b664e1da7f3a4c64af3fbd4012bfb44d56)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial fix for [YOCTO #5368]
Updated the figure to not have the tarball method in there
for setting up poky repo locally. Also, added specific references
to the environment setup scripts.
(From yocto-docs rev: 7c6ececaf8eb987206567077f42213dbe4cdc4f2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial fix to [YOCTO #5368]
I updated the workflow so that it does not have the tarball
extraction option to set up local copies of poky and meta-intel.
The figure is housed in dev-manual and mega-manual.
(From yocto-docs rev: d70214d7d348d38b574561339987bd3371167a48)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
Partial fix to the tarball removal issue. I rewrote parts of
this term's definition to slightly de-emphasize tarball expansion
as a method to set up the Source Directory on the local machine.
(From yocto-docs rev: 2fb1e569129e9942ca4a99fe7f73de02ccbd1876)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
This is a partial fix to the removing tarball setup method issue.
I have modified the "Yocto Project source Repositories" section to
de-emphasize the tarball installation method for poky and meta-intel.
We cannot remove these obviously because the download page of the
website gives the use access to tarballs. Also, the Index of
Releases basically does the same thing. So, we can't ignore the
fact that they are there. So, I added a note basically saying we
recommend the Git method for creation of poky and meta-intel on the
development system.
(From yocto-docs rev: 7843ea5e592582f74a02536ec4057067c43eb507)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
Partial fix for this issue, which is removal of the tarball install
methods for poky and now evidently meta-intel. This commit removed
the tarball install step for meta-intel in the "Supported Board
Support Packages (BSPs):" bullet item in the getting setup section.
(From yocto-docs rev: 98f13d8178a63258e2b80d78796e473d09abb452)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
Partial fix for the bug. This part removed the tarball install
method from the getting setup section of the second chapter. I
did some rewriting to smooth it out.
(From yocto-docs rev: b051433e34e0f3a46deba0b2b4815ab77fde62c8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #4414]
Some changes to the toaster section according to the updated
toaster wike site and Belen.
(From yocto-docs rev: 1e66b4d377c21fae179826dab5ceb75b9aea1a1b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
Applied some review comments from Laszlo to the new description.
I added an example.
Reported-by: Laszlo Papp <lpapp@kde.org>
(From yocto-docs rev: 5961cde05aff967f8db7cd10cd9b46c147c62f83)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
The current explanation was ambiguous regarging the term
"subset". I have rewritten to be clear.
Reported-by: Laszlo Papp <lpapp@kde.org>
(From yocto-docs rev: 3bf41e856c3d9828d5c9cd6d70467e88a4af575f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Broke up the introductory paragraph a bit because it was one
large chunk of text.
Added the release variable to specify the directory in which to
find the environment setup script for the toolchain.
(From yocto-docs rev: 82f4a35fa29526fcfa4041c410b52f9c87ec939a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section pretty much sucked. I did some re-writing and
created a list to better present the material and options.
(From yocto-docs rev: 4bd833d2a0f55865d9f35784fbfd3c00ebc2daea)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was a bit confusing. I added some lists to make
it clearer when this step is necessary. I also added some more
detail on where to find the setup script.
(From yocto-docs rev: 0518aeeb0b395c84233bace26fc3f40234e044b3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed a grammar issue and provided some wording to make things
clearer for locating the Makefile.inc file.
(From yocto-docs rev: b734fddeb700a0e2e685e8453395653926dbabe6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added in some enhancements here:
1. Worded the local build environment setup stuff to include
the possibility of memory resident version of BB.
2. Make a better looking list.
3. Dumped the note about changing directories after running
your setup script.
(From yocto-docs rev: a19874c2b01a38b72fc02e9ae373c335f1dfbef7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was not quite right for the installation method
after obtaining the tarball. There was some old stuff in there
and it didn't mention the fact that the script asks you what
directory you want to install into.
(From yocto-docs rev: b49c86a1a447a8d39b0054a480fb5d4b6f608297)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The path used for the toolchain was wrong. The string
"toolchain" appears in the path. I was not informed of this
before locking down 1.5 release doc changes. I have updated
the path in the "Using a Cross-Toolchain Tarball" section.
Occured twice.
(From yocto-docs rev: 307f570b3bc253ef110553d950c1f2a43396b908)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5368]
Partial fix to this issue.
This section demonstrated how to build the ADT Installer tarball
using BitBake by downloading the poky release tarball. I updated
the section to use the method where you use Git to clone the
poky repo and then check out the current release as a branch.
I also re-organized the section to read better.
(From yocto-docs rev: 116779a3fa776a4eeb283b238bc2b5fb7202ffb4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>