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>
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 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>
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>
