In the Kernel example appendix I changed some remaining 3.2
kernel strings to 3.4. Also I added the OE_INIT_FILE variable
from poky.ent for use instead of the "oe-init-build-env" string.
(From yocto-docs rev: 1d9d8d72d197bdd81756eed7fe1529f341de6089)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Each time the kernel revision is bumped (e.g. 3.2 to 3.4)
Some of the figures would be out of date. The reason is they
had pathnames that included the release of the kernel.
For previous YP releases I was adding logic to the Makefile
to be sure to catch the right files dependent on the branch
from which the documents were being built. This scheme is
not scalable so I decided to make the figures generic by
adding a note within the figures explaining the place-holder
"<x.x>" as part of a pathname. Thus, three new figures were
added to the folders directories of the dev-manual and the
mega-manual. Correspondingly, the 'denzil' version of the
figures were deleted.
I modified the Makefile so that if the BRANCH is not edison
or denzil then the generic figure set is used. I have to retain
the logic for both edison and denzil to cover the case where
a user clones or sets up an edison or denzil repo and then
builds out the manuals. Basically, it had to be backwards
compatible for releases prior to danny.
(From yocto-docs rev: 8283eed4b0b9ec164b87db99c35231f8731ac443)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor edits to the part of the example that sets up for the
first core-image-minimal build. Put in the variable to use
for the build environment setup script, updated some changed
output from some of the commands, etc.
(From yocto-docs rev: 0b4b2ddf9a78a9d6d218ed9a6f0acd3e876d9581)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Danny, the "kernel-example-repo-<release>.png" file changed to
"kernel-example-repo-danny.png". To correctly make the dev-manual
and the mega-manual some things needed to change:
1. New figure created and added to both the dev-manual and the
mega-manuals figures directory.
2. The "kernel-example-repo-denzil.png" files from the dev-manual
and mega-manual figures directory was removed.
3. The Makefile was adjusted so a new BRANCH=danny area now exists
to set TARFILES for both dev-manual and mega-manual.
(From yocto-docs rev: 8b2ff6b657a1486559799e219baaec9fde2e5c6c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a note at the beginning of this appendix that references
the yocto-kernel script as a way to quickly manage kernel patches
and configuration.
(From yocto-docs rev: 35cd7f6a9722120e47ae8b422dd86593497ebf1c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#3180]
Final changes to the packages section. They were re-organized and
the set is complete and thus fixes this bug.
(From yocto-docs rev: 533b45c9d41330497bbd0da58b812a4738ba64a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This appendix is antiquated and needed removed. The BSP
development example is now in the BSP guide where it talks
about running the yocto-bsp script.
(From yocto-docs rev: 892ff450d79a7564a72f11eb7510d349ca71d47a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removing the Appendix A (BSP) example had some rippling affects
throughout the doc set. There were several links into the appendix.
All these links had to either be modified (if possible) or simply
removed since the appendix will be removed.
(From yocto-docs rev: fff35abd87e945de1806eef63a56a956d104bf92)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section now points into the BSP Guide where it talks
about using the yocto-bsp script to create a BSP. The prior
method was by hand and described in an appendix (A) of the
YP Development Manual.
FYI - this results in the removal of Appendex A in a future
commit.
(From yocto-docs rev: 5e1c44b1768b79dd1447ea47461b84248bd2111f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A few edits to the respective sections that talk about required
packages. Some wording changes for headless and graphics
supported systems. Also, re-inserted the note about older
CentOS systems.
Reported-by Paul Eggleton <paul.eggleton>
(From yocto-docs rev: 112370758cf41104ff04c4996d4a432e6bd54be1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a walk through of the "Using the Yocto Project's BSP Tools"
section. Updated included altered output based on the current
example commands and scenarios.
Also made changes to the bblayers.conf file as the default
version for this file has changed.
(From yocto-docs rev: d8a2195e37d8f96702026e42bb43daf39852ffcb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The examples were out of date. They did not show the
meta-yocto-bsp layer, which is there now by default.
(From yocto-docs rev: ea2e2e8a259bc3e629fb8087229872b9818a696a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section was out of date. I copied in the most recent version
of the bblayers.conf file, which sets LCONF_VERSION to "6" now.
Also, added the meta-yocto-bsp layer to the example.
Additionally, I inserted a Note explaining the consequences of
removing the meta-yocto layer. The note references [YOCTO_#3176]
for more information.
(From yocto-docs rev: 532b72c5c18b2a9a61619164bae6216c91c2ecc9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current setting was changed from "1" to "6".
(From yocto-docs rev: 7f5be4b0b2d1e17add774c7ba3b8803ad770a8fc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the meta-yocto-bsp layer to the example listing in the
"Enabling Your Layer" section.
(From yocto-docs rev: 95fb13a1049ccaffb3531c93a28a3c480ea1a243)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the meta-yocto-bsp layer to the example.
(From yocto-docs rev: be4ee9d08527b654071b8d4ff54ad978f50a98f5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The term should be initially capitalized.
(From yocto-docs rev: 38a11d512bfe675319fb76da9d7618315af91c47)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reorganization of the packages section in the YP Quick Start.
These are now ordered still by distro but the listed packages
have been culled down to just the needed ones to run an
image on QEMU with graphical support.
A corresponding section in the reference manual now provides
the comprehensive list of packages for all supported distros.
The section in the reference manual is broken down by
distro and by function.
Finally, four new variables were introduced to track the
essential packages for each of the distros. The variables
are defined in poky.ent and follow the form
<distro>_HOST_PACKAGES_ESSENTIAL. This will make it so
we don't have to maintain this list of essential packages
in multiple places.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: 839b441791980db82f4795454e976e606b486d25)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently. The faq entry changed is
"How does Poky differ from OpenEmbedded?"
(From yocto-docs rev: ecc88ef12ec2faa48d05824e8b781a7d43e86127)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The entry for the question "Are there any products using
the OpenEmbedded build system (poky)?" was updated. The
changes result in a better question and answer.
(From yocto-docs rev: cfc4a945738e891d20ab1a2a7002c5c421b0a225)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Explain that we test with a set of reference hardware rather than only
supporting hardware that we have (avoiding any implication that the
build system can't support other devices). These are in the
faq entry in the poky-ref-manual for the question of how we can
claim Poky / OpenEmbedded-Core is stable.
* Adjust the language so that it is OE-Core friendly, with a link to
the Development Manual for the definition of OE-Core.
(From yocto-docs rev: 5ff1604dd383b26e918c319fcbe46dd1589cebc5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we are using a layer-based approach, people do not
need to rely upon the Yocto Project team to add support
for new boards.
(From yocto-docs rev: 569ff9da7443f9654f288d0a4e62ef06ba34ba52)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I edited the patch from Paul a bit here to conform to
the style of writing plus to make things clearer.
(From yocto-docs rev: 87abf857cfcd8a0d78a48322fbe9ac5395b6ad30)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Took out the FAQ question about using Ubuntu Intrepid and
seeing build failures.
(From yocto-docs rev: 2885aa27904d4b31541f77ceeb54ad94a8e21378)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adjust a few sentences so that they make better sense.
(From yocto-docs rev: 67437c9f31fca0437e1f23ab78dd252f3ca0a903)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add new SDKIMAGE_FEATURES to variable reference.
(From yocto-docs rev: bb7de36ef04a11c95c46c8fbbe170c721d7b020b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Document the new staticdev-pkgs IMAGE_FEATURES item.
(From yocto-docs rev: 64317edb209b8f9c720c4b1930a0d355d2db6b38)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the listing of the final SRCREV statements for the
BSP example.
(From yocto-docs rev: 0d0d5994c2653dda1171eaad226bbe1764a04440)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These changes are partial for converting the example for BSP
creation from Crown Bay to Fish River Island 2.
(From yocto-docs rev: c7fc78a8453ad363138764aa30e377b56ce49f2b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed the reference to the Downloads page.
Also fixed the local branch in the meta-intel example so that
it uses the same name as the local branch created for cloning
poky.
(From yocto-docs rev: edac781b37bce0d0bca6a741186cfa53a512b73e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new branch is named distro plus poky revision
(e.g. danny-8.0). I had just the distro in there.
(From yocto-docs rev: 9490849f7f6dc815d1b676b15b3f38f671a49be8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The term "Source Directory" should be capitalized.
(From yocto-docs rev: 143213545358dd5b6c28c71202bea2e40dbb2522)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the Quilt and Git flow methods there is a bullet that talks
about incrementing the PR variable. I changed the wording to
be in the context of recipes rather than packages.
(From yocto-docs rev: 64f6230251c023e469a346c0425834b950ed5c9b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example that describes changing the source code usees the
P* variables extensively to refer to names of the recipes. The
wording used was antiquated and exclusively referred to
"Packages." I changed to reflect the fact that P* variables
in general are refering the recipes and not the packages.
(From yocto-docs rev: bd3ef1c46fc7a3b0b2ff5ab60dc52e125f080e24)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
some of the links to information for the user-space tools
had become obsolete. Fixed them.
(From yocto-docs rev: 84e72204e34e45d9d8cae876710a46a83b61c0cc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the preferred branch for the Eclipse example from
a hard-coded "1.3_beta" to use the DISTRO_NAME variable.
(From yocto-docs rev: 9393c5d1e44a1e326c73353b090c1d1c1a5833da)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added information in the #4 box to include the cross-dev
toolchain.
(From yocto-docs rev: 198ab4326369d8c74225d9de51bf536621ab2251)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the item that talks about getting the root filesystem.
Realized that the cross-toolchain was not discussed in this
bullet for the case where a user does not use the ADT
Installer. Added text and references to correct that.
(From yocto-docs rev: ec2f5103471f047f7ed7e53cc22789c74ab506ae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added an earlier occurence of the "tm" for Eclipse product.
Also, changed the reference for modifying the kernel to point
into the appendex rather than self-referencing the same section
from where the reference originated.
(From yocto-docs rev: a85840611650c9124b6194acca59c8bfe71f566c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I standardized the use of the term "Source Directory" when
referring to the poky directory as set up on the host.
(From yocto-docs rev: 3eaf7a734a4eecab2be2c8e71bee4d6c2cb7788b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made this more accurate by including notes to edit the
source and use of menuconfig within the diagram.
(From yocto-docs rev: 91d3d2e935aab24c4bd96c5921a605cbbb7e3231)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to add the 3.4 kernel to the list of linux-yocto-*
kernels as found in the source repository.
(From yocto-docs rev: 98538e2616214f76083697ad3cc886efd183c34e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bulleted item that describes where to look for application
development was still pointing exclusively to the adt-manual.
Updated to point to adt-manual for host setup only and then
point to section in the dev-manual for the Eclipse example.
(From yocto-docs rev: 36ac631e23366c4d9f83c2d00cbbd3bc4758aa15)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Better display of the SELECTED_OPTIMIZATION variable options
when they appear as a list.
Also, some punctuation added.
(From yocto-docs rev: 73777e545f13eacca9ee466ba852bccd84c17f6f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
'sdk', when used in general terms should be capitialized.
(From yocto-docs rev: 1d68746ae197620b533a9ad53e71b16c9e4e42b8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found other changes for underlying/corresponding wordings
regarding the relationship between .bb and .bbappend filenames.
(From yocto-docs rev: 28f12a4ea97a683281cd8cc0bbceb40d2b896aa4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Better choice of word here is "corresponding" rather than
"underlying".
(From yocto-docs rev: 3d8b6d6e06b81960df2a7d25b6d54308210cc011)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The manual listed an out-dated example listing of meta-* layers
in poky.
(From yocto-docs rev: 39e2a02301d1d0b609fbc041395dd31f6ba9fa2d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The description for where the "scripts" directory lives was not
conforming to our terminology.
(From yocto-docs rev: 925167c446b86ca09d387d01568db64113412311)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For obvious reasons I changed this one :)
(From yocto-docs rev: 5f3203292f46bea799321e4520668252a46fb599)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I improved the wording such that it is not tied to a
x.x type release. It is more generic here and will survive
better under future releases.
(From yocto-docs rev: 2bd644db7fef71cd2f07f6d3dcbd2ba60b83df08)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a line to cd to the poky directory so the example makes
sure the meta-intel directory is created in poky as it states.
(From yocto-docs rev: fdeff0fc2c61c521eaf9d3c48429792f1559c2a4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated so that the repo poky-extras is for sure created inside
the poky repository.
(From yocto-docs rev: b01ea76ded2ade66f2cb19b37d9e9d8d5d2e96c9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
changed the example of what the manual does not provide to
be more appropriate.
(From yocto-docs rev: c4e7712cfd2e13b42f7322ffed6a1f84116df963)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Turns out the .sh file that installs the tarball comes down without
executable permissions. I added a sentence in each manual instructing
the user to set the permissions to the script before attempting to
run it.
(From yocto-docs rev: c1699971b3e03893aa1af5033e19d8f5c0b21ff4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#2930]
You can now select the install location directory instead of
automatically going to /opt/poky. Some small edits to the
section that describes what happens when you fire off the
adt_installer script.
(From yocto-docs rev: 57f34c9b3a82222ed0ffc99e998614884b9a3486)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new paragraph to the section that talks about getting
images to state that if the user is not using or building a
core-image-*-dev type image and they want to develop against
their image, they need to be sure to include the development
packages in their image recipe.
Reporte-by: Jessica Zhang <jessica.zhang@intel.com>
(From yocto-docs rev: 8da6f6172d3ad27c1cf6d52fd3d029d75ec9d0fd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Section A.5.2.3 "Changing recipes-kernel" indicated that the user
needed to look in poky/meta-yocto/recipes-kernel/linux to find
the linux-yocto_3.2.bbappend file to locate correct SRCREV
values. With 3.1, the team split out kernel and BSP stuff
even further by creating a poky/meta-yocto-bsp directory.
The example needs to reference that directory instead.
(From yocto-docs rev: 6e9b0ceb5ad24b1be8399bf5a0a83fdc30129f82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#3095]
A minor edit to the glossary entry. The fix for this bug spanned
two other commits:
418862011e79940ee378f64c6171618d29568014
7647cef96643b3723f80013c2c51ba6d7480122a
(From yocto-docs rev: 053e4558cc90eb1618e697394aff6d40edbeb3b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These edits removed the .x eplanation at the end. Paul Eggleton
concluded they do not matter and are confusing.
(From yocto-docs rev: 3f3e0b65bbfbb8da3ba1ebbb8dc78c3adf5a1c98)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a malformed line in the example. It needed a space,
which I added.
Reported-by: Brian Lloyd <blloyd@familyhonor.net>
(From yocto-docs rev: 892062d46463237375c49772cadb03356f636a82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A re-write of this glossary item. The example provides more
detail and frames it in the context of a real example.
(From yocto-docs rev: 1a88abecf6ab5895d3c8ff801bd869a90a8a3fc1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the wording in the front to get rid of redundancy
and specifically state that this variable affects .bbappend
files only.
(From yocto-docs rev: 7647cef96643b3723f80013c2c51ba6d7480122a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the glossary description for the B variable. There
was some confusing "source directory" terminology in there.
(From yocto-docs rev: 72fbf86ca9612a0dca741f08315efed1d9efa0b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the section "Using an External SCM." This section was
written so that PN was refering to a package instead of correctly
refering to the recipe.
(From yocto-docs rev: 2bf44cf78bef08d2dd4d9e596100900913777d60)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new glossary entry for the BP variable.
(From yocto-docs rev: a6a8f7ad9157932799eb3e3d0bbffdf93ed70c0e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a glossary entry for the P variable.
(From yocto-docs rev: f1d65b7cca35bdfaad029523de0d88d4e009f82a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a first draft of the glossary term PRINC.
(From yocto-docs rev: 418862011e79940ee378f64c6171618d29568014)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new glossary entry for the PF variable.
(From yocto-docs rev: 1ad43661638ab9ae8a3af9d6149f6af633bdece2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some clarifying edits to the explanation about suffix and
prefix names used with the PN variable.
(From yocto-docs rev: f42baf8ddb3da1ab8ba69d30581812646ce4dc83)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Checked and fixed all text surrounding the description and use
of the PN variable. This variable can mean a recipe or a resulting
package depending on context.
(From yocto-docs rev: 7ac52f6b184670db9cdab7c205126b62c60b0d29)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Re-write of the SRC_URI glossary entry so that proper terminology
for PN is used. This context the PN refers to the recipe name
and not a resulting package.
(From yocto-docs rev: fc371890d9797ba57e2ce848cd2f82f42dd6ac36)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#1939]
Added the option downloadfilename to the SRC_URI variable
glossary description.
(From yocto-docs rev: abc32d85a7f241766d1fcc52a251249f2172ea89)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#1939]
Expanded the definition for the SRC_URI variable in the glossary.
The new information includes protocol types and SRC_URI options.
(From yocto-docs rev: 033d58cd2ec2a579fa085bcca1e5d0ad4dd65708)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replaced with the variable OE_INIT_FILE.
(From yocto-docs rev: 1deaa02f29b2a4b9cc7ff3307c8a3ebd0dfb9623)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A few minor corrections to fix some wordings.
(From yocto-docs rev: de71001992150da685a70389e28313df609d6521)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the example that builds an image so that it uses the
default build directory. It seems like the natural thing to do.
Also added a new poky.ent variable named OE_INIT_FILE. This
variable is set to the name of the build environment script
(From yocto-docs rev: f0db49e27e89aefb6d43a0b455c6ecc529399c27)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For 1.3 there is not longer a toolchain tarball. Instead, there
is a wrapper script that lets you install the tarball. This
fundamental usage model change caused several ripples throughout
the documentation set. I have changed wordings and examples
to reflect the new paradigm.
(From yocto-docs rev: afb2069daa91e04c0f78ba425a6b184cb820d888)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The steps for creating a project in Eclipse vary a bit between Juno
and Indigo. These changes reflect that.
(From yocto-docs rev: a020ecde8ed02a29f67498ef1511261d2054f784)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a couple of reminders and some links to information about
separately extracting and installing the sysroot filesystem.
(From yocto-docs rev: d340dcb5021fe1dcdaae0830ef8624c0fc54bedf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added text indicating that the user is prompted to verify the
cross-toolchain installation location.
(From yocto-docs rev: 3226eb2f0807687e8685702850a3a12b3d60ae5f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a command to the example that places the user in the
adt-installer folder before they attempt to run scripts/adt_installer
for completeness.
(From yocto-docs rev: f098e1095d24d0271fb21f50aa848ebc05b828b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Edits to test out the lastes version of installing the Yocto Eclipse
plug-in from the latest source. Small changes to be more complete
on the step-by-step process with regard to being in the right
branch. Also, inserted 1.3_beta as the version. This will change
later.
(From yocto-docs rev: 1326916a7d03bdbb0613e6e26a4089b3bd87d204)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I fixed the repo example so that the -b option is right after the
git checkout command and so that the "origin/" string is part of the
example.
(From yocto-docs rev: ba7ed26cf308a69e1ec8cfb0072dd10742af4ac5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Slight wording change to the description of the
PACAGE_BEFORE_PN variable description based on feedback from
Paul Eggleton.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: 8f7dcdb8edf461133d2149eb4728ee3682affc98)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the variable from BB_ENV_WHITELIST to BB_ENV_EXTRAWHITE
in the text before the example line. I had the wrong variable
in there.
(From yocto-docs rev: f909a7336ae2f95baa751231beeae08081576e1f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #2904]
Added glib-gettextize package to the list of required Fedora
packages.
(From yocto-docs rev: c46f8e46ad70bf979d2e51e58d461bcd9456b773)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the BitBake "Preferences and Providers" section to remove
references to these two Pimlico applications that have been removed,
and tweak the example slightly so it is technically correct.
(From yocto-docs rev: 744624a40d02a859b3c526f5ea6657d32edd39c6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
List frameworks we provide that are likely to be used by people these
days - Pimlico has been removed and GuPNP and Matchbox don't really
belong. Also slightly modify the sentence following so that it is clear
that these are optional.
In addition to Paul's patch, I cleaned up one of his sentences with
some simple grammar edits.
(From yocto-docs rev: 1cdeb057bab0d69fe6656e33e643962dd2086567)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-core was renamed to core-image-x11 and the editor and file
manager were removed.
* core-image-basic's description has been updated to reflect its
intended purpose
* core-image-lsb is intended to be standalone - should not be
associated with core-image-basic.
* The Pimlico applications have been removed so they are no longer
present in the Sato images.
In addition to Paul's patch, I removed the "etc." word. This word
is better replaced by "and so forth". Also, consistent with the
YP documentation.
(From yocto-docs rev: aba7ae60a38dfeda9ef52237b81f387984621847)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a short section about packagegroup.bbclass.
In addition to Paul's patch, I changed the title of the cross-reference
to be the actual title used in the YP Development Manual.
(From yocto-docs rev: bfd4db7e0ef61a2dd7159cdc841dcffc2d9c53d4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* For PE/PV/PR/PN these pertain to a recipe ("package" was used here
historically).
* References to variables should not be prefixed with $ in the text
* Add text about suffixing RCONFLICTS as per other package variables
* Make ALLOW_EMPTY example complete
* Clarify and add example for AUTOREV
In addition to Paul's patch, I re-worded two instances. One
to get rid of "package(s)", which is poor form. And a second
to get rid of "unstable/development", which is also poor form.
(From yocto-docs rev: 498349f8d82f46433626521d148ff6c1d72e2b1c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Clarifying who picks up files that would normally be included
in the default package. This is a wording change to try and
eliminate the ambiguous "they".
(From yocto-docs rev: 63f87b6616c1a93d39e198f0b02d01d36ac09467)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the "Reference: Images" section to "Images". This old
name was a hold over from when the book had appendices that were
reference-like. Along with changing the name I also fixed two
links to the section that were found in the variables chapter.
(From yocto-docs rev: e21a973cfe07d21acdfe02b49aa86c7672905968)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also add a definition for PACKAGE_BEFORE_PN since the default
value of PACKAGES now includes this.
In addition to Paul's changes I reformatted the default to be
<literallayout> to appear as code.
(From yocto-docs rev: 187390e2589b886e524700db9dc2e89cf28c6e90)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These file paths are no longer valid, instead point to the section
of the reference manual with more information on valid IMAGE_FEATURES.
In addition to Paul's patch, I provided the actual section name for
the cross-reference link he inserte.
(From yocto-docs rev: ad356708bfe3a14e82d678510df15cb93dc2f057)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apps-console-core has been effectively replaced by splash
* apps-x11-core, apps-x11-games have been removed
* ssh-server-* were added quite a while ago, add these here
* x11 has been added
* x11-base has changed behaviour slightly
* doc-pkgs was added
* nfs-server never exported the entire /, so remove this comment
In addition to Paul's changes. I performed some general edits to the
list so that it is active voice and has a parallel structure for
all the list items. Changes involved some of Paul's stuff and some
of mine.
(From yocto-docs rev: fec6f162506a59124b137a7d1640944114ebb5c2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Task has been renamed to package group, and there are some minor changes
in how package group recipes should be constructed - in particular the
inherit of packagegroup.bbclass is now highly recommended as it will set
appropriate defaults and automatically add complementary -dev and -dbg
packages.
In addition to Paul's patch, I added a couple <filename>/</filename>
tags around some switch names to be consistent with manual
formatting.
(From yocto-docs rev: 598d18507ace2054f8c8bb5f496557c98f066b5a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-intel BSPs and yocto-bsp tool no longer use a bbappend of
task-core-tools-profile to add systemtap, so these sections should be
removed.
(From yocto-docs rev: cdc12163dd95f0a78cc0f35c03b5eb3d7b1476e3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert P. J. Day pointed out a link in the development manual that
was for the BitBake User Manual. The link resolved to an old,
non-maintained version of BitBake documentation. According to
Richard Purdie, the BitBake docs referenced should be the ones
that ship in the bitbake/doc/manual directory of poky. The
YP docs had been using a variable named BITBAKE_DOCS_URL that
also resolved to the antiquated user manual site. Consequently,
there were many links that needed fixed across both the YP
Development Manual and the YP Reference Manual. Each of these
references now points in general to the bitbake/doc/manual
directory in poky for more information.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 12f77236b602e9ec43e845c8cec060ad342af19c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note in the "Creating Layers" section noting that to be
Yocto Project compliant, a layer must contain a README file. This
change was prompted by a discussion over the fact between Robert
P. J. Day and Mark Hatle.
(From yocto-docs rev: 2e073763a81125699a2d962031ca29ca64c81595)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I think I got it right this time... sheesh. Had the wrong
file suffix in there for the .tgz file.
(From yocto-docs rev: d5931252ede475846dcb61fc0e0f03eb7fe4015e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #3036]
Turns out the fakeroot package is not required for the Fedora
Linux distribution. I removed this to reverse the fix I did
earlier for YOCTO #3036.
(From yocto-docs rev: 6b22dda7fc7f07bd34d2a84e03308ae8ebcfbe9b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor wording changes.
(From yocto-docs rev: 2744ef171c4454ce66aee240963c34bc326f1c07)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #3036]
Added fakeroot to the Fedora package list. Removed python-curses
package from the Fedora package list. Added python-curses package
to the OpenSUSE package list.
This fixes a previous commit where I accidentally added python-curses
to Fedora.
(From yocto-docs rev: 8e1b7a640886e6d39cf1e175611098555204a5f3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #3036]
I added the python-curses package to the list of required packages
for the Fedora distribution.
(From yocto-docs rev: 2929a0f97cd9be88580c0a80848b7fff327b4642)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This new directory contains the files for the mega-manual HTML
document. Mega-manual is a compilation of all the existing YP
manuals and guides. It is a single HTML file that simply lists
each individual HTML document for the existing YP manuals and
guides. The figures directory contains all the figures (duplicated)
from the individual manuals and guides.
(From yocto-docs rev: 5620c20ea4c7c69c96601b7480471e6166fd9409)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added this file to the tools directory. It is used from the Makefile
when making the mega-manual. The file processes all the appropriate
<ulink> tags so that they are converted to <link> tags and the user
is not vectored off to an external HTML file.
(From yocto-docs rev: da2ad62a160c22f785e8237439494716e4c023cd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the section that describes how to submit a patch through
email while not using the scripts that send patches and request
pulls.
(From yocto-docs rev: 9167b89289134d8d16610cc527d0d71713c0641b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the title and a single reference from the Kernel manual
to a title more representative of how these patches are sent -
not using scripts.
(From yocto-docs rev: ff908c34fae88eab9724891a008142a834f34081)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added text to indicate that using the two scripts for generating
patches and requesting pulls is the preferred method to send
a patch.
(From yocto-docs rev: d6f036a91074dd00c51fe0f937224182fc801b3b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the section heading for the part describing how to
push changes upstream via the poky scripts. Also had to
change one cross-reference to the section in the kernel
manual.
(From yocto-docs rev: be7712aba044238e8781cdf869c5d14e77eb09a2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Every place in the YP documentation suggests setting BB_NUMBER_THREADS
and PARALLEL_MAKE to twice the number of cores as the host machine.
This fixes a single instance in the YP dev manual where it was
suggested that PARELLEL_MAKE be set at 1.5x times the number of
cores.
(From yocto-docs rev: b6b820371cbe43e39425156c72c45df283fdf7d1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added information about the mega-manual.
(From yocto-docs rev: bbf75682f957ad2e124aa9476f52cd2bd3829fa6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three things done to the Makefile:
1. Added logic so that the user can generate the mega-manual HTML
document. It includes processing links using mega-manual.sed
2. Added and updated the comments for 1.3 and inclusive of
mega-manual generation.
3. Added a test for the existance of HTML file in the publish
task. Previously you got some error that was geeky.
(From yocto-docs rev: 99b865ab96b086d818375d1c00f98a3e3a4f4e9f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed "The" from all the titles of the books. This makes it easier
to reference to them and easier for the automated processing of the
mega-manual.
(From yocto-docs rev: af566d6d007cff642648698ea487a6eeaa8cc930)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I fixed a reference to a manual that should have had "Guide" and
not "Manual"
(From yocto-docs rev: a51de96fe0cd78cb379e6758d7e357c91daa2791)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I fixed several occurences of cross-references to whole manuals where
the formatting was split in the <ulink> statement. The <ulink> tag
and the manual title must be on one DocBook line in order for the
sed scripts to correctly process the links when the mega-manual is
created.
(From yocto-docs rev: 0dee12d518c892f59c0446e1c7b5d0f71b6ee22b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed several references to books. There should be no books referenced
using "The" at the beginning of the manual title. These need to be
"the" in order for correct mega-manual link processing with the
sed script.
(From yocto-docs rev: 76753216c7138d55f7b6f9167d678245ab3134e7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
the title in the note about production process was technically
wrong. I added in "Yocto Project" as part of the title.
(From yocto-docs rev: c421f02549b8ca203d1c9f747870911c59bda96c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
the notes that say "Due to production processes..." at the start of
each manual contain links to manuals. the links needed to be formatted
such that the entire <ulink> code and manual name appeared on the same
line so that the sed script can effectively remove the link in the
resulting mega-manual.
(From yocto-docs rev: 0a41971c331ad1961e6ee1e067b59c36c9f048f6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I moved "the" outside of the generated HTML link so that the sed
script will process this part of the manual correctly for the
HTML mega-manual.
(From yocto-docs rev: 3bdf7c7dc4478f2a435cbc84a8a815daf7130660)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The references to the YP Development Manual were inconsistant.
These references were fixed.
(From yocto-docs rev: f4ded0b965fcbce7b500ca21886ee9b755c38383)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The way I refered to the YP Quick Start was inconsistant.
I have made edits to remove these.
(From yocto-docs rev: d9487c60db23861e8a9dd2c81ac46d4960abd462)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added new style.css names for the individual manuals.
Also, created a new entry for the mega-manual. This will generate
an HTML file only (similar to the QS). No PDF file will be generated.
The entry creates an appropriate mega-manual.tgz file as well and
can be branch-dependent (like the dev manual) since it will
obviously include the dev manual.
(From yocto-docs rev: be8c0b965a89e3517a09647eeda06c2ff163d260)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had to rename individual style.css sheets to have book-specific
names. So style.css for the ADT manual becomes adt-style.css and
so forth. Turns out, this isn't really necessary for the solution
to create the mega-manual but I am leaving the changes as a
separate commit because it makes sense. It causes no disruption
to making the six YP manuals.
(From yocto-docs rev: 8cbdae1fe86988243f91dfd611c14f8a37007886)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For some odd reason the PNG filename for the YP logo did not end
in "p". I added the character so that the image is displayed.
(From yocto-docs rev: a6a4bcf9798be2bbf1be3922226ef83b7d6667d6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed a couple of id strings so that they are not duplicates.
I did this to eliminate a make error while experimenting with creation
of the single HTML YP document comprised of the individual docs.
Changing the id strings has no consequence on the individual Application
Developer's Guide and Kernel Manual.
(From yocto-docs rev: 4e6832eca319a637be693dfe67ee56c540dfddfa)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a read-through of the manual and spotted several nits that
I fixed. All these are minor fixes.
(From yocto-docs rev: 0c8f9c660ecea0b36e2b6af0315d3d239f70a688)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the first sentence of the description of how to use QEMU images
with NFS server. This is feedback from Scott Garman's review.
(From yocto-docs rev: 6a33b1b58bd72756baf57228b7348ff662248012)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #2929]
Provided an updated section on how to install and configure the
Eclipse IDE so that it supports both Juno 4.2 and Indigo 3.7.2.
The fix included creating a new poky.ent variable that is
Juno-specific.
(From yocto-docs rev: 6b0b046322420f56feb644eb6de8341dfac59df2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added clarification on how a user can hand-delete images from
the build/tmp/deply/images directory.
(From yocto-docs rev: 4655085d43b36b024a2e01cfcc7455e18d891ab8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated an old comment in the layers.conf file example to say we
have recipes-* directories instead of the old packages directory.
(From yocto-docs rev: c39394e848d6039e6728b7e53de86958f951e258)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two areas of the manual updated to reflect the fact that not all
QEMU images have an SSH server in them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a173d8cb05ee695b02188a037ee047db016c6a67)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the decision to create a single HTML file that has all
individual YP manuals, the need for including the BSP guide as
part of the YP Reference Manual goes away. I have removed this
guide as a chapter, removed the mention of it in the introduction,
and fixed the two links in the FAQ chapter to reference the external
manual.
(From yocto-docs rev: b0dbda9e09b73c2b26111bda118731dbb3090cae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The detailed chapter that describes how to install and configure
the Eclipse Yocto Plug-in has been moved to become a subsection of
the "Workflow" chapter in the YP Development Manual. This commit
accomplished the bulk move, edits to integrate the information,
and fixes to all cross-references. Moving the chapter creates a
sectioning issue in the YP Development manual that results in
subsections that are six levels deep. Not ideal. Will look at
fixing these with a subsequent commit.
(From yocto-docs rev: e6abff8f578f2cf6997895260f607395281ae8e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The name of the ADT manual has changed to the "Yocto Project
Application Developer's Guide." This change had some ripple effect
regarding cross-references into the manual. These are now fixed.
(From yocto-docs rev: 7ba25c470b03a85098388e6cca7c78a6ebb245d8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In preparation for taking the Eclipse installation and configuration steps,
I have made an edit pass through the section "Workflow Using the
ADT and Eclipse". Minor edits performed to integrate the new
information.
(From yocto-docs rev: 7b4e0ae371b23f329451ac768b7d9eab5931df2d)
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: ef6888dffa95e1fbf74dd80e48034f3591a32959)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the creation of a new KMACHINE glossary item, there were two
areas in the YP doc set that reference the variable. I added
cross-reference tags. Also noted that some other references
were missing to the variable COMPATIBLE_MACHINE.
(From yocto-docs rev: f740b62be175a50f17ce8a244258dcf391fcf672)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a new glossary entry for the KMACHINE variable. I used
Bruce Ashfield as my resource for understanding this variable.
(From yocto-docs rev: 1069ddb3fe0b3bd00ba651b51419354258ae57d3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have updated both the section for configuration fragments found
in the BSP and dev manuals.
Reported-by: James Abernathy <jabernathy@gmail.com>
(From yocto-docs rev: 62f4df751c80e7b749356bb80ade3a7847411f7c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We should not use "latest" any longer for this variable. The
string is fine in URLs that might appear on a website but the actual
variable should be set to the release number. This way when we
go to release the version of the docs they do not have to be reset
with a post-release commit to change the variable from "lastest" to
"1.3".
(From yocto-docs rev: f97122847e65c223173fabb793ef1ddb04605e62)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor edits to create some links to some terms used.
(From yocto-docs rev: 1559b8caca07cce8630de9ddf8c84f0b24fa35e7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made a pass through this chapter and focused on better descriptions for
getting the system ready for application development. I made adjustments
to better represent what is really being done. It is not all ADT here
as was being described before. Miscellaneous edits and improvements
throughout.
(From yocto-docs rev: 3544beda4794005fe139d7620fd13618fab05534)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I edited the text so that the purpose of the manual is clearer.
I have segmented out the ADT into distinct components and made sure
the overviews of each is good. Edits to clarify the role of the
ADT as well.
(From yocto-docs rev: c4abd8305dcdba986f1e761887c740e8322bb331)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
figure updated to reflect new manual title.
(From yocto-docs rev: 420bad21ffe1d1fd60a1bbbe66f3e1463b80cff9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
final changes to the section that talks about configuring the kernel.
Changes here based off Bruce Ashfield's review comments.
(From yocto-docs rev: 7715643f2a24336585dd44d1d75e7be0aade7f6b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The string used for the link anchor for the "What You Need and
How You Get It" section in the YP QS used "resources". This
string is actually used as the chapter id for the resources
chapter in the YP ref manual. I changed the string in the QS
from "resources" to "yp-resourses" to make it unique. There was
one instance in the YP ref manual where a cross-reference to the
section occurred. I fixed that as well.
(From yocto-docs rev: 58c1e4e327cb489e037bbde170c4c495f4567392)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Caught and fixed a stray reference to "appendix" that should be
"chapter."
(From yocto-docs rev: 97d26495dd9b561bb5724a86e9cd777eeef9f71a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Converted the "Resources" appendix to a chapter. I also made sure all
the references to the chapter use proper term now, which is "chapter".
(From yocto-docs rev: bf7212b72d54a2696c16dcc1c0a19681f23fbc1c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "faq" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 6e090132823e3b121d00d9116b0693c922156b32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-varlocality" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: d666a3f6581bb114c6c15d63ef850678c398b247)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-varibales-gloss" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 3f541c20c7aff1012eb4c06cb856bf9795124822)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-imagese" and "ref-features" appendices
to chapters and made any references in the doc set use the proper
term now (chapter).
(From yocto-docs rev: 08117634034a5cd5567c971957583d986c9ee9a4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-classes" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 54991c7fb0a2d3a894249f8a253b1a974cf2e571)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-bitbake" appendix to a chapter and
made sure the single in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 1086155dd6e67a9c75e99332a9ad122dc04ec7a1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-structure" appendix to a chapter and
made sure the two references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 840a3e4dab355e53fdb400674bd6765957b24066)
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: ddee80872afc567b9381387980f257b337f29ea1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removing the Development chapter resulted in some links being
re-defined to go to the YP Development manual. Also, the
poky-ref-manual.xml file had to be altered to not include the
chapter. Any sort of residual cleanup needed as a result of
getting rid of this chapter is handled in this commit.
(From yocto-docs rev: f8d113654b33ed5f6f1ba8e2d2e755b78033ddbf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Development chapter has been emptied out so it is now deleted from
the reference manual. All relevant topics now reside in the YP
Development Manual.
(From yocto-docs rev: aa30971ea0b23c19e3fefcb48db8aa4c0db8e95e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the section "Using an External SCM" to the "Common Tasks"
chapter. This information was formerly in the YP Reference Manual
in the old development chapter.
(From yocto-docs rev: d34cd9e86cb7a6b27cf6a5b4daf58c445dd86331)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the "Development Using a Development Shell" section. This
section was moved to the YP Development manual into the "Common
Development Models" chapter.
(From yocto-docs rev: 4222ce12d620bf3cd98ae80b19402cf59cca3d3f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I inserted the section "Using a Development Shell" into the "Common
Development Models" chapter. This information was formerly in the
YP Reference Manual and is being moved out to help the ref manual
become a truer reference manual.
(From yocto-docs rev: f4ca1c567afcebbae119f21c147e3c38c7ffd54e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a scrub for "Yocto Project" and found some that could be
changed.
(From yocto-docs rev: 985062b6a9320e8a3ca3d3dafb6516db4fbc5bd5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the FAQ entry on "How do I use an external toolchain."
Comments were from Richard Purdie.
(From yocto-docs rev: db3986d2eff17087eb141ac0f4dfed55ff753368)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a bit of detail to the install toolchain example to explain
that the user needs to be in the root directory.
(From yocto-docs rev: afb294f6e0997b72f11d9e9d31b3b22d083c2dad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New finalized entry for KBRANCH. Reviewed by Bruce Ashfield.
(From yocto-docs rev: 566e112d20ebe91a1302263b96254f6f66462aaf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some work in progress.
(From yocto-docs rev: d344b2db75c21bc7050e4a5f70c07ffd8f7545de)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I missed a "Yocto Project Files" term because the damn thing split
across two lines in the source file and my grep method did not find
it. Changed it to "source directory."
(From yocto-docs rev: 31a261c141d3e26f4a87b9725097005c96345e2e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mentioned at the very end of the beagleboard build that the image
can now be run on the target hardware.
Also, specically noted the local.conf file as "conf/local.conf" in
the build directory.
Reported-by: Kevin Strasser <keven.strasser@intel.com>
(From yocto-docs rev: a4b41c7f5e8e8017401961097e0df4b13458ac24)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor fixes to some links and some typos.
(From yocto-docs rev: 8d1f53bca404461f8edc526d5e144ef7d76f0594)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a scrub for the term "Yocto" and substituted appropriately.
This resulted in the term "Yocto Project build system" going away and
being replaced by "OpenEmbedded build system." The "Yocto Project
build directory" was replaced by "build directory." I also found a few
little things that were wrong like including the Debian distro in the
list of supported distros so I removed that. Finally, a spell check
produced a couple of fixes.
(From yocto-docs rev: 6957658982516aa4b0e4726c9344c46854aa11d3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I fixed several "Yocto Project build system" terms and some "Yocto
Project Build Directory" terms.
(From yocto-docs rev: 10c1d50380336ac684243525646ac9aa3c1812d4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a stray reference to "Yocto Project Build Directory." I changed
to "build directory."
(From yocto-docs rev: e0c593ac162c61f7d42625482b95c253d0f8622a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the build/tmp/log directory description to mention that running
a build does not necessarily mean a log directory is created. Also,
ran a spell check and found a typo.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: c602919a1f188a4dff23f965bcc52b635f9a92ae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
the section describing meta/recipes.txt had the "/" character at the
end of the filename, which is incorrect. I removed this.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 28295d8c46d3a2cc6b53f0a7ccea35f1db77d1df)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made a few edits to better describe how the scripts and bin/bitbake
directories are placed into the PATH variable.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 1e45731898935d40db6e6705f60bdea9633255ab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The description of how BitBake is run and where its executable and
wrapper script reside has been updated to be more accurate.
Reported-by: Robert J. P. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 885b4c42a3ec3d228f1f5659a887627f4fe2d939)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on "Dependency Graphs" failed to mention the
package-depends.dot file among the files. Added this file to the
list.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0ebf8ddf54e146454d6f300f790964decaeec6a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
this information was missing in the appendix.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 64ea0871e0a6cef45259502ff26e1c5b5a66cac1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Information about this directory was absent in the manual.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 64e5f5a403e4c8494885c7da504194d1baecb0ed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#2671]
Added a bit more in here about considering requesting rights to have
a contrib area to YP and OE if user is a regular and significant
contributor.
(From yocto-docs rev: b54bba33b2706bed593a9ee66d5c72f820c37d32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section that describes how to send a patch upstream via email
did not have a good connection to the various mailing lists. I
added some references to this section and also mentioned using
the scripts if the user has many changes to commit.
(From yocto-docs rev: ad75ae45420c43bda974d22b02094237b5c7cc50)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bug 2256 is now fixed in master and the fix will be in the next release,
so update the documentation accordingly.
(From yocto-docs rev: 877a7ecfd1623417d0793a5dd16b66c35b6fdbae)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
"shared state cache" is the generally accepted term for this.
(From yocto-docs rev: a15f629afe46e7217182a1ac077ab59641be9a8c)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It's CONFIG_SMP here, and since the title of the section already
mentions it, just change the sentence to be more generic.
(From yocto-docs rev: 32e6145b5f41d4eb293f8267ef01d02217143152)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Change some of the language and patch submission directions to
correctly represent how we work together with OpenEmbedded (this
changed with the introduction of OE-Core a few releases ago).
* Correct --help option to -h for pull request scripts
* Clarify commit message guidelines
* Touch up a few other bits and pieces
Fixes [YOCTO #2671].
(From yocto-docs rev: 3170ce5e0757951afee13207c117316e33449b39)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need to include the OpenEmbedded and BitBake mailing lists here as
they are an integral part of the community especially for patch
submission.
Note that this supersedes the information about mailing lists in the dev
manual (which should be replaced with a link to this section).
(From yocto-docs rev: e9bae0a323af2d95505c5492be985232440842ff)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have changed as many "Yocto Project" terms as possible so that
better reflect reality.
(From yocto-docs rev: 5f729e53b0cb653c97621e4e6598d9295d60ada5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Got rid of some old author text.
(From yocto-docs rev: 358ff9b2de4196d23a51215ea56193fa23ebaa1a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed all occurrences of "Yocto Project" to terms better suited
to reality.
(From yocto-docs rev: fdd7b8c2bcbaf566cad336c67c582c2a24aa9dc1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Throughout the manual, the kernels that are built and available through
the Yocto Project were being referenced as a "Linux Yocto kernel."
This reference is poor. First, it placed Linux and Yocto very close
together and could upset the Linux folks. Second, a better way would
have been to say "Yocto Linux kernel." I have fixed by referring to
kernels that are available through the Yocto Project as
"Yocto Project kernels."
(From yocto-docs rev: 9b8319328cd4ab4ce3363001c9feeec585d9cab9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have replaced the term "Yocto Project" with more appropriate terms
where possible.
(From yocto-docs rev: 622ef9a2b4897ecd151b641b43d7706ab673c989)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scrubbed the manual for the term "Yocto Project", which has been
over-used. I updated occurrances to better represent actual bits
rather than generically referring to everything as Yocto Project.
(From yocto-docs rev: f70cffeffa0d8863a88783607621bf6f7125d02d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pared down the use of the term Yocto Project.
(From yocto-docs rev: d62747ca1d42cae703d1cd307dfe16bb9682b741)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes throughout the manual that either eliminate or change
many of the "Yocto Project" strings. The file structure for
the meta data is now called "source directory." The build
directory is referred as just that - "build directory." Any
where the build system is referred to it is called the
"OpenEmbedded build system."
(From yocto-docs rev: 1210c19f90d4a52042fec12657212ae3e58e13d6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new FAQ entry on how to get rid of build output and
start over. Sourced by Robert P. J. Day.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 3b94911aaf64b9618f8dbc0d8b98384b9ebd33b4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have cleaned up a bit of the FAQ entry for how to use an
external toolchain. This is not complete yet.
(From yocto-docs rev: 030324a6881d8b9b0bcf476a2b7bfdd6fbd978a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Cleaned up the glossary description a bit.
(From yocto-docs rev: 344ff68ebb58f4ea62d6cb052b712466f593a9f2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example did not specify to switch to the "denzil" branch after
establishing the local repo of poky-extras. The example will not
work without this step.
(From yocto-docs rev: 90071570bca2edfceb4adb91bdd9093c095c8825)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note to warn the user about mixing ADT Intaller installation
methods.
(From yocto-docs rev: 718a48a7ea4753eb1e59e17a75c3d94a9ed166bb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previous renditions of the term "Build Appliance" referred to the
VMware system. However, it was determined that the term
"Build Appliance" should really refer to the actual image that
can be booted and run on the VMware applications. I have updated
the areas affected by this change. The change assumes the name of
the built or downloaded file you boot will be named
"build-appliance-image."
Fixes [YOCTO_#2656]
(From yocto-docs rev: 6b27b7d92b9722351eb43a7c2a341ce3af056dba)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The dialogue for the Yocto Project Settings is now "Yocto Project
Settings" instead of "Project Yocto Settings." Updated the manual.
(From yocto-docs rev: 980b4d22dab4ac681c6dc1a85e78306213799062)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The selection "Yocto ADT Project" has changed to "Yocto Project ADT
Project."
(From yocto-docs rev: aa61cd4f93e08373ef430926c008da9f28f72ff8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section that describes how to generate the cross-toolchain into the
Yocto build tree erroneously referred to this process as installing the
toolchain. Furthermore, it actually mentioned the creation of a
toolchain tarball, which is wrong. I updated the section to more properly
refer to this procedure as generating the toolchain. I also removed the
bit about the tarball creation.
(From yocto-docs rev: 5ae8faa651ed6bf22c5475a4eacb5c758c62cea1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The item to click in the step to configure the Eclipse Yocto Plug-in
changed from "Yocto ADT" to "Yocto Project ADT."
(From yocto-docs rev: fc860fe497be6da189e8e48f9546b105b9ff0075)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is important that the environment uses a host gcc when running the
adt installer. I put some text in noting that.
(From yocto-docs rev: 7f63662913d6d79843e1bdcadc49bb120bb72688)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor typoes in first couple chapters
(From yocto-docs rev: 36618cc6a261a994b00c5c524c76cbf3952a2eae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The sections describing how to debug remotely and how to use the
oprifiler have been deleted. these sections are now in the YP
Development Manual.
(From yocto-docs rev: 5f277a38a7afe1cc06eafe2ef1b07cc24c8ec546)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Moved the sections on remote debugging and using the profile out of
the YP Reference Manual and into the YP Development Manual. These are
now two sections in the "Common Tasks" chapter.
(From yocto-docs rev: 42640bf69aa05c56eb112c10b6d7b96069173785)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the "Development Using Yocto Project Directly" section.
This information is better covered in the YP Development Manual
where it talks about modifying temporary source code.
(From yocto-docs rev: f3c8c182a8b34c8fdfe4be8c497948f8b777ddf2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section "Modifying Temporary Source Code" that was in the chapter
for "Common Tasks" was moved to the "Common Development Models" chapter.
After discussion with Darren Hart, modifying temporary source code
is a valid develop model. So, rather than isolate it in the common
tasks chapter it has been placed in the development model chapter,
which now has four types of development.
Changes were made to update the introductory text of all the concerned
areas of the manual.
(From yocto-docs rev: 8b07ee3bcda9c13e576b54b0079b0656cd8fcc32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section "External Development Using the Eclipse Plug-In" is
redundant. We have an entire chapter in the YP ADT manual for
this information. The section has been removed.
(From yocto-docs rev: fa9d4785032aada0a52acd1cec083d00dc4ac21b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section "External Development Using the Meta-Toolchain" was removed.
The information in this section is better presented in the ADT manual
and in the YP Development manual.
(From yocto-docs rev: 2488d6ac9872b00a8887a12a6c77aa16d30ad5e4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three cross-references to the section "External Development
Using the Meta-Toolchain" were removed. This section is going
away in the YP Reference Manual. There is no replacement section
that makes sense so the cross-reference is removed.
(From yocto-docs rev: 97ed489c335d6d2782cc3ed684fce92c78b4fec8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a small review comment to the section based on reviewer
feedback.
(From yocto-docs rev: 68cc2bac8dca78572d197af326452bbd37c947f9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Using Pre-Built Binaries and QUME" section needed to incorporate
some information from the YP Reference Manual. I have merged those
changes in and did some re-writing to blend it well.
(From yocto-docs rev: 5c20f00f9ec75c19fd0106c9f241751381ba7e3c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the section about developing binaries using QEMU. This section
is better placed in the YP Development Manual.
(From yocto-docs rev: 83a4e84b69051f217993d80b525e9d07d64d1c6d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Inserted a note warning the developer that it is their responsibility
to understand and meet all licensing requirements if they are going
to be including images as part of a BSP.
(From yocto-docs rev: b8154904be02a4185bf417f193eb125b8470bc8d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Implemented review feedback from Dave Stewart and Tom Zanussi.
(From yocto-docs rev: 5ed73c29b6a46737a009a38b294bdd61e4c63d85)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the "Requirements and Recommendations for Released BSPs"
section. This section was requested by Dave Stewart based on
community input for direction on how to create a BSP that was
compliant with the Yocto Project. The input for the section came
from Tom Zanussi.
A spell-check was performed also prior to this commit that addressed
a few spelling issues across the file.
(From yocto-docs rev: 7ed0dd1093b33491231dec06f7b5f8e76004130d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the "Show a Particular Feature or Branch Change" section so
that it reads better. I also included some real examples.
(From yocto-docs rev: 42aa13c7fbf45abf869b056deec063be6682c70b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
According to Bruce Ashfield, we will be using linux-yocto-3.4. So
I changed the linux-yocto-3.0 strings to linux-yocto-3.4.
(From yocto-docs rev: 23df0251b04ed7c31ad2297a4a7870861554beef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I removed two larges sections of old comments.
(From yocto-docs rev: df1b08b621f2b449c7575b86ec90c40f1606c43d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated a note to include information about what happens if you do a
kernel build and have your machine compatible with every possible
kernel. This extra information is useful for rational.
Reported-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From yocto-docs rev: e631ec44be49d456add6a53ff3db89016d187370)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example showing how to use pre-built images, the toolchain, and
filesystem was off a bit. I changed some wording to indicate using the
.ext3 filetype of the filesystem. Previously it talked about expanding
the tarball version but the example has been changed to use .ext3.
Also, the environment setup file has been mis-named forever. It should
have i586 in it and not i686. And, finally, the image name does not
have a release number as part of the name.
(From yocto-docs rev: c9953c9bb716ae5be183020c5143152226bf1de5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The linux-yocto_3.2.bbappend example was out of date. There is no
longer a kernel features statement in the last part of the section.
Only COMPATIBLE_MACHINE, KMACHINE, and KBRANCH remain. I removed
the fourth one from the text description and the example code.
(From yocto-docs rev: 1a6d3cad48f1b52e5b029434ce655940c6024694)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note telling the user that the commit ID strings in the
example might not match the actual commit ID strings found in
the .bbappend file.
(From yocto-docs rev: 5cb845361c8ce8b60dcafc28d1bc01d54badd67a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #2459]
I provided better definitions to the -dev and -sdk image types.
They now call out host development and target development.
(From yocto-docs rev: bd2c0db27d7eb038931550a96752f961ea6b1d9c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The description had reference to a toolchain, which is evidently not
true. I have re-worded the description so that it does not mention
inclusion of the toolchain.
Reported-by: Wolfgang Denk <wd@denx.de>
(From yocto-docs rev: 5a918d7d20133b85badd082c81cfe4af18709316)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #2445]
Added a note telling the user not to install Eclipse from the distribution's
package repository but to rather be sure to install from the official
Eclipse download site.
Also, changed the tarball name from having a "3.7.1" in it to the
recent version of "3.7.2".
Reported-by: Lianhao Lu <lianhao.lu@intel.com>
(From yocto-docs rev: f50d0071e39a5e8424633a55ab2c3fdc75e9686d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to a bug (2256) the example that changes the kernel configuration
through menuconfig did not work. I have re-written the section
to now start with the default behavior of CONFIG_SMP=y and then
have the user change the configuration to where it is not set.
The changes include the reversing of the flow and the work-around
needed due to bug 2256.
(From yocto-docs rev: 6fa9eee12ed83f81470beb9792fb4fc1c5104f69)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added entries for the Manual History table for upcoming 1.3 docs.
(From yocto-docs rev: 430b384035593cd05c4f286e20c01f0fe72da8ec)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To publish manuals for the "latest" set of docs, some variables
need changed. DISTRO is 1.3, DSTRO_NAME is 1.2+snapshot, and
POKYVERSION is 8.0.
(From yocto-docs rev: e5a21791b4e588631910f102b660c1709ab7a0f4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove mercurial as this is no longer needed.
linuxdoc-tools was mentioned twice in the CentOS list.
We no longer support Fedora versions older than 15 so remove this note.
This commit applies to 1.2, 1.2.1, and 1.3.
(From yocto-docs rev: 4a7e8cc3d69d5c2f9aacedc5f7e2ff9657ef850f)
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>
I discovered a bug when publishing documents. There are two scp
commands that copy a document's files and figures to the appropriate
directory in the srifenbark@yocto-www:~/www.yoctoproject.or-docs
server where the manuals are published. The second scp command
had a "/figures" at the end. This was causing a new "figures"
directory to be created within the "figures" directory. This
redundancy shows up as missing figures in the manuals if a new figure
or changed figure is ever added to the book after initial
publishing. I removed the extra "/figures" at the end of the scp
command.
(From yocto-docs rev: cef3634e695f61bfb8465f1fb7a88e4e8a9a00f1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Need quotes around the INHERIT statement.
Reported-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
(From yocto-docs rev: 96f03be0d2595b4b788d8bb2110fe8801279f3f9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example that compliles the altered code will not run now when the
KMACHINE statement is in the linux-yocto_3.2.bbappend file. I have
commented it out of the book.
(From yocto-docs rev: 3f67b34daf1ad598b4d07f5e2a60d8c63da754b2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The KSRC example needs "_3_2" at the end of the variable.
(From yocto-docs rev: e6bcbe8504f72777a03e9b08de95d5e2741700a3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Turns out the KSRC_linux_yocto ?= /home/scottrif/linux-yocto-3.2.git
statement in the linux-yocto_3.2.bbappend file in poky-extras needs
quote characters around the pathname. I updated the example
statement.
(From yocto-docs rev: eac1b53c04398152b41ac280fdc030615c165112)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found two instances of "yocto/standard/common-pc/base". this should
now be "standard/default/common-pc/base".
(From yocto-docs rev: a2f4ac3885de1157e6d718cfea9b29a67c76aeb0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel used for example is no linux-yocto_3.2. I changed
all occurences of yocto_3.0 over to yocto_3.2
(From yocto-docs rev: 7ee8f86fd0f44197901c851a16c58aa5f6851b1f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example code with the printk statements needed to be altered.
And the wording supporting the example was modifyied to be more
generic.
(From yocto-docs rev: f76465e920c3959230196814f17890065c613730)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Looks like calibrate_delay(void) changed in the example. Updated
to the most recent code.
(From yocto-docs rev: f1abcbf730c4b50ceb925e41181429c04eb2d55e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the example sets up the bare clone. The shell output changed
because the upstream repo changed to
"origin/standard/default/common-pc/base".
(From yocto-docs rev: cc3a8dde7b7f70174225ec95303d0280697d674b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A new figure was needed in the Kernel appendix. I added that
figure to the block of code that creates the tarball for the
denzil branch.
(From yocto-docs rev: 352093f3eabf64052d78a41fd997993d09aa10ef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New image needed for Denzil. I created a new file named
"kernel-example-repos-denzil.png" and copied it to the
Figures folder. I also deleted the
"kernel-example-repos.png" image.
(From yocto-docs rev: 97105187735c15e452580a0174897517c1860f2c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Building and Booting the Image" section there is an example
.hddimg file. I updated the file to be the actual file used during
the BSP example build.
(From yocto-docs rev: 165feb4d501a2ed984b742ea9f10e6c2037972da)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For 1.2 you evidently need to add $HOME/poky/meta-intel to your
bblayers.conf file.
(From yocto-docs rev: d5565d9aa14590622373996a037cc16d34e9107f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Wording for linux-yocto_3.2.bbappend file updated to support the
addition o fhte KBRANCH variable.
(From yocto-docs rev: 267d7dffc05dc495dbd27b6435bea7ba48cd4cfa)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
edited it to now include the PREFERRED_VERSION variable.
(From yocto-docs rev: 72d8f7bfcad0fff191c998f90369499a78d62696)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on changing recipes-kernel was way out of date.
I updated all relavent changes.
(From yocto-docs rev: 91538864e6da8c4d0a495e52feafe01ce7afea9d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kernel used in now 3.2 and not 3.0.
(From yocto-docs rev: 974cb0c3665a2767a04ab6261692e93cc2f9200b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The layer.conf file now uses a LAYERDEPENDS variable. I added that
to the example.
(From yocto-docs rev: 237eb7ba897479935ac4c3165ce2cb350143a1e3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel in mymachine.conf had to be changed from 3.0 to 3.2
(From yocto-docs rev: cd94a4d45a062e9282de15dfda25983c500c0548)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The output for creating and switching to the denzil branch
for meta-intel needed updated.
(From yocto-docs rev: ad29c8f73ab3cec930f21939744cff322b43dfdc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The variable substitution had to be changed from
"&DISTRO_NAME;-6.0.0.tar.bz2" to "&DISTRO_NAME;-&POKYVERSION;.tar.bz2".
(From yocto-docs rev: 258b4c7fb46d2e6fb2da7bf2f59cd4f5c035b15b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a link to the Yocto Project Files term.
(From yocto-docs rev: 9d92248cb5dd862095e815c008e1f47e7518856a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Had to remove "poky-" from the front of this variable that resolves
to a YP Files top-level name from the tarball.
(From yocto-docs rev: a9ccf2bec4f2f916e854d10aa992f0c45eb0ed3f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Throughout the documentation set I have refered to the YP build
system generically in order to avoid use of the "Poky" term. Richard
has suggested that we refer to the actual thing that does the building.
So I have added BitBake to this particular sentence to refer to the
tool.
(From yocto-docs rev: eaed76bbf97bd34205eace952a1efbc600890815)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This file was replaced by a release-specific file named
"kernel-overview-3-denzil.
(From yocto-docs rev: 85220f16ce10086372f9d81c61cb4e3eb40d52e4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
dev-manual/dev-manual-model.xml: The Bare Clone and Copy of the Bare
Clone figures are out of date for denzil. These needed to be
re-done so they use "linux-yocto-3.2.git" and "my-linux-yocto-3.0-work"
as the root names. This presents a Makefile issue when making the
denzil and pre-denzil versions of the manuals. Whenever you use a
different figure for a different release, you need to involve the
BRANCH variable in the Makefile. This is necessary because you are
using different figures in the generated tarballs. The set of figures
could be unique to the release. The outdated figure is
"kernel-overview-3.png" and will eventually be removed (later commit).
I created a new figure named "kernel-overview-3-denzil.png" and used
that in the dev-manual-model.xml file.
documentation/Makefile: I updated the Makefile to test for a
"denzil" release build and if so include the new file in the
generated tarball. This commit adds the new .PNG file as well.
Fixed the Makefile so that if you don't supply a BRANCH value, it
uses the latest figures (denzil).
(From yocto-docs rev: b3550d7640343cd5459efb04c591b81a1e41bc1b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the Note wording to work with the list and not be specific
to a number of supported kernels.
(From yocto-docs rev: 04b941264c001fc2f8e105637436b8d95a770357)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list specifically named four kernels supported. I changed it so
it would say "several kernels".
(From yocto-docs rev: 8134eae4bce85e18a4402606e2cac6cb422cf0cf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several things out-of-date for step five of the BSP Creation overview.
(From yocto-docs rev: 6bf1c93315c2fe604dbe468a29d9e2159bf7aceb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link and wording to the YP Downloads page on the website was
wrong. Fixed it up.
(From yocto-docs rev: 191856e4441bcea078868d22d019f4f1cdd62512)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more detail to the pathname for the example
formfactor_0.0.bbappend file.
(From yocto-docs rev: 4bd9ac9f189689ddb8806c750545223e1e55cd4b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed a reference to Yocto Project Files and provided a link.
Put in an updated version of the meta/recipes-bsp/formfactor/
formfactor_0.0.bb file in the example.
(From yocto-docs rev: 031113db6d67beaee2e4f8225c7d4d2bc9380b05)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated various shell output examples created from cloning various
Git repositories, etc.
(From yocto-docs rev: 76024b2648c383bf19e6fee81d54c6a992e8d593)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the shell output example when user creates a bare clone
of kernel. We use linux-yocto-3.2 here.
(From yocto-docs rev: 69e3aa7a42d03cff23379432f5d1b496157d5c0d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example that creates a local branch based on a release tag
in the "Repositories, Tags, and Branches" section was not optimal.
Darren Hart informed me that naming a local branch the same name
as a tag confuses Git. Plus, the "-b" option was mis-placed.
Renamed the local branch to have "my-" in front of it and moved
the "-b" option earlier in the command.
(From yocto-docs rev: 29f4ea267ef687431e09eca4634fcb6cc48a6f81)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example in the "Repositories, Tags, and Branches" section that
creates a local branch that tracks the upstream branch is incorrect.
The syntax should be "git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME;
Fixed it.
(From yocto-docs rev: ec80d43ad97370771c9cd7f7e6a4637db5f80e9b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added Hob and Build Appliance to the list of other stuff the user
might want to reference.
(From yocto-docs rev: 4c94654e53e422e5e0a54476e3ca88e682f177af)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Better wording for the role of BitBake. Updated shell output for
the clone of poky.
(From yocto-docs rev: eab184de2bd2b22def9dbe0c93b153ec9334402b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The following packages no longer need to be installed on the host
system:
* python-psyco
* help2man
* cvs
* hg
Additionally, linuxdoc-tools was mentioned twice in the Fedora list.
(From yocto-docs rev: 89fc20a1a54f92165323cb2dbcfc5063c0205369)
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>
As suggested by Paul Eggleton and Richard Purdie, the example that
describes another method for creating a cusomt image was modified
so that it is based on an existing recipe instead of requiring a
new image.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 65287ca135422a588d799143d93ccd4d058684ff)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scott Rifenbark
Paul Eggleton
Ross Burton
Robert P. J. Day