Changes include:
* Updating all the Manual revision history tables for 1.8.2
* Updating the poky.ent file with new variable values for 1.8.2
* Updating the mega-manual.sed file so good links are generated
for the mega-manual
(From yocto-docs rev: d77321f4bef95c48d1df8b671418ebb4fa68bd66)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Involves setting poky.ent variables, updating the manual
revision tables, and editing the mega-manual.sed file to
have the 1.8.1 string in there.
(From yocto-docs rev: 5f06e00c9bd657059433cd3487e86eccd31e5cd6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made several changes as Toaster will not support using the
'master' branch now.
(From yocto-docs rev: cc7e1273944d72388ba4202cbf7146a909d1cdac)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7925]
Changed the final example from "useradd" to "usermod".
(From yocto-docs rev: 4360a2ab5734d456648efd72df6b1de4a3980ded)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In Section 5.5.3.2 bb.fetch.encodeurl: Use bb.fetch.encodeurl
changed to
bb.encodeurl: Use bb.fetch.encodeurl
Reported-by: Olivier Dugas <dugaso@sonatest.com>
(From yocto-docs rev: bb8e0c173d4c1945ab538a33c7c868f0f72fd362)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed wording in section 7.78 to use "nativesdk-myrecipe.bb".
Fixed message to say "non-dev/-dbg/nativesdk- package contains symlink..."
Reported-by: Rene Fichter <rene@fichter.se>
(From yocto-docs rev: 429fd10005c4e63c611eb8192a71f063310f8933)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7755]
Applied some review edits to the wording from Ross Burton.
(From yocto-docs rev: da0642350520975416d1c91ac98b57a6bde26439)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a clarifying paragraph at the start of the section that talks
about building on the target hardware. Included kernel-devsrc and
rationale for why a user would even do this (it is not normal).
(From yocto-docs rev: 95ae213b80cb45b5e9b7b161b2968dca6315e1da)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Once again... having to try and match what is done by the release
team. I think going forward we will use this form for
YOCTO_RELEASE_NOTES
(From yocto-docs rev: 7745eb618d7ab6e01e98d2158599047486649e4a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added information to note when it is used (insane.bbclass) and only
if the recipe inherits the autotools.bbclass.
Fixes [YOCTO #7755]
(From yocto-docs rev: 1a30a52c90a77990e9fd178837102b7f1978d7e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #6611]
Added a new step to the "Working With Your Own Sources" section
so that the user is aware of needing to provide a defconfig file
or configuration fragments to the SRC_URI variable when working
with the yocto-linux-custom.bb recipe.
(From yocto-docs rev: 7a24ea3ce2f732baebbdb4fb42d458901ff056d1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added information in about the various varflags the user can
use to define the type of archive.
(From yocto-docs rev: b3dbe2410e67c3b9988d11c8f9e105c4d01ce22e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7474]
There was a TBD section here that needed filling out.
(From yocto-docs rev: f82a5ea99f8b3d6dfc7fc38148b5e6e5e4721b05)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the new section "Using an "In-Tree" defconfig File"
section. This section addresses the ability to not use the
default location for defconfig files, which is usually in the
metadata layer. The section describes how to use the
KBUILD_DEFCONFIG variable.
Fixes [YOCTO #7474]
(From yocto-docs rev: f514c8b96ef991f5893c73ae06392eb306c12a5e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Configuring the Kernel" section did not address "defconfig"
files. In my opinion, this is a hole in the docs for this section.
I added a new section titled "Creating a defconfig File" that is a
sub-section of the "Configuring the Kernel" section.
Additionally, I added a brief sentence in the introductory paragraph
to include the fact that this new information exists.
Finally, I included the bitbake command that ensures that the
proper configuration steps are minimally run before a user attempts
to use bitbake to get into menuconfig.
Fixes [#YOCTO 7474]
(From yocto-docs rev: 3e982a4f19402a941583a9a8708eeb6dbaf8fad5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7474]
The "Generating Configuration Files" section has a procedure that
starts with a step to complete a build at least through the
kernel configuration task. This is needed but we could use a
bit of explanation here. I added some rationale behind why you
should do this.
(From yocto-docs rev: dc6579de0740703796e7e6473ad86f70d0ca5aa2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The customization layers were pointing to Sourceforge site for the
XSl files needed to build the manuals. Throuhgout time, this site
has failed me enough to warrent trying to get these XSL files from
some other source. Rather than ship the XSL files with the YP release,
we decided to create some mirrors and point the customization files
there.
(From yocto-docs rev: 280bcafb4ce3471c364612aa85f7280f700f855d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable has been deprecated a while and Paul Eggleton suggested
we finally remove it from the glossary. I removed it and also
took away the two links from where the variable was referenced
in a couple spots in the migration section.
(From yocto-docs rev: 141b873f6c3111c791fdc71f937b667171f82d2e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7755]
Added a new description for this variable. Based it on information
given to me by Paul Eggleton.
(From yocto-docs rev: 112b86020942939a00a742d5aa421a23f2651a97)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added better wording to show that you use spaces to separate
multiple features.
(From yocto-docs rev: 5bbfda659be29b0014d25391680c1f9e4f3866d1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section needed some more information. It referenced the yocto-kernel
script and menuconfig. I added references to the appropriate areas of
YP documentation for these. I also changed wordings to that it is
apparent that .config is created by menuconfig when changes are saved.
(From yocto-docs rev: aa01fd8d5917fac6c14f69aaa0a26200b3e67968)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The way to include tcf-agent now in an image that you are going to
remotely deploy and debug using the Eclipse IDE is to simply include
the eclipse-debug image feature as part of the image. I updated the
section around getting images to reflect this simple method.
Reported-by: Adam Lee <adam@gumstix.com>
(From yocto-docs rev: 2da55c34972f4e6a57c37a9011c2c4769a0e3814)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed [YOCTO #7632]
Looked for, updated, and added (if necessary) the following
variables:
* ROOTFS_PREPROCESS_COMMAND
* ROOTFS_POSTPROCESS_COMMAND
* SDK_POSTPROCESS_COMMAND
* POPULATE_SDK_POST_TARGET_COMMAND
* POPULATE_SDK_POST_HOST_COMMAND,
* IMAGE_POSTPROCESS_COMMAND
* IMAGE_PREPROCESS_COMMAND
* ROOTFS_POSTUNINSTALL_COMMAND
* ROOTFS_POSTINSTALL_COMMAND
Each of these variables no longer accepts arbitrary shell commands but
rather functions. The wordings now support that behavior.
Also, updated the migration section for going to 1.6 release to note
this change.
(From yocto-docs rev: d52256cbf08a4d8968d68423138546fb33abbad6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I applied a little more information to this section to help
round out the variable explanations. Part of the change involved
adding PARALLEL_MAKEINST to the list of scaled variables.
I had left that variable off. Also added a new trade-off.
(From yocto-docs rev: 2b6377030677b1318cb9d6e038885d7874f0e609)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated both the PARALLEL_MAKE and PARALLEL_MAKEINST variables
by expanding the note to indicate how to prohibit parallel make
threads. Also, added a cross-referencing link to the
"Debugging Parallel Make Races" section.
I added a short note to the start of the "Debugging Parallel Make
Races" section noting that if they can't properly fix the condition,
they can always do a work-around to set the PARALLEL_MAKE or
PARALLEL_MAKEINST variables to null.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 8c0dc2540e97a4e3a42c1d541ea20e65518fffef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added some more detail to these two variables. The system sets
them according to the perceived number of cores. These default
setting are cool for single socket systems. However, if you
have some big system with a lot of physical CPUs, you might want
to cap off the values at 20. This is according to Darren Hart.
I also put in some cross-references to the "Speeding Up the Build"
section.
(From yocto-docs rev: 69b931f019f7bec687a642d7fccd1172a9be1746)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7665]
Added descriptions in the glossary for the following variables:
* SDK_HOST_MANIFEST
* SDK_TARGET_MANIFEST
* SDK_VERSION
* TOOLCHAIN_OUTPUTNAME
(From yocto-docs rev: 709421023ff6545da30fcb3486027ff984d4241e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the "Optionally Building a Toolchain Installer" section
to emphasize using 'bitbake <image> -c populate_sdk' as the method
for building outa toolchain. Before the change, equal emphasis was
put on for this preferred method and the 'bitbake meta-toolchain'
method.
(From yocto-docs rev: 46156957c38edf33cf3c98957733f6eb4323fa0b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7524]
The "Writing New Tests" section needed more clarification in the first
paragraph. One requirement is that minimally, an empty __iniit_.py
file must exist in the runtime directory.
(From yocto-docs rev: 8f003a9fe7c31bad7ed705a003a44761ba8b3c4f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also, added a cross-reference link from the archiver.bbclass section
to the new description.
(From yocto-docs rev: 1a7c86064f2dbb7453026bf8b8166566b33b3287)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In response to community input where developers were attempting to
locate information on how to write packages out to a directory
other than ${DEPLOY_DIR}/<package_type>, I updated the "Package
Feeds" section, added several new DEPLOY_DIR_* variables, updated
four classes, and updated four tasks. Here are some details:
* Made changes to the "Package Feeds" section to provide more
accurate information in the package feeds directory structure
used by the build system in build/tmp. These changes included
updating the figure itself and some explanatory text.
* Updated the DEPLOY_DIR variable description.
* Added new variable descriptions for DEPLOY_DIR_DEB, DEPLOY_DIR_IPK,
DEPLOY_DIR_RPM, and DEPLOY_DIR_TAR.
* Updated the related classes: package_deb, package_ipk, package_rpm,
and package_tar.
* Updated the related tasks: do_package_write_deb, do_package_write_ipk,
do_package_write_rpm, and do_package_write_tar.
Reported-by: Trieu Nguyen <trieu.t.nguyen@intel.com>
(From yocto-docs rev: a8d499850dec72f8decd81ec6714809c3a580ffc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the requirement that debug-tweaks is needed in order to
individually use the allow-empty-passowrk, empty-root-password,
and post-install-logging features. These three features can be
individually turned on an off regardless of debug-tweaks.
(From yocto-docs rev: e9f2e2b0f094cf243d601ee3fcdf9588cc81e003)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding Luna and dropping Juno. Pretty much went through the
"Working With Eclipse" section and dropped Juno and added
Luna. A major deletion was the BitBake Commander section using
Hob. Todor told me to drop this section completely. Note that
I also added a couple new YoctoProjectTools that appear on the
menu: SystemTap and yocto-bsp.
(From yocto-docs rev: 6dc7d842acb0f190138418c7bf874999219cbead)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7630]
I applied some feedback from Laszlo Papp suggesting that the user
can also use '-fpic' as well as '-fPIC' for a command-line option.
(From yocto-docs rev: 750ff4d3203f358595df8d10cc57e8d63a9fef4a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7386]
Apparently the "‐" ENTITY used throughout the YP manual set to
get literal "-" characters in example commands renders into a unicode
that is not a dash. This results in users getting errors if they
attempt to cut-and-paste a sample command that uses a "-" character
from the manual into a shell. I have universally replaced all the
"‐" strings in the YP manual set to "-" strings.
(From yocto-docs rev: 1309e124d83fdf3c98be5c3ff1943f1c0d496c20)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GNOME Mobile no longer applies. I updated text to use the
GTK+ wordings.
(From yocto-docs rev: 978878d3f1a7ea07a68f0aeae93eeae7ba58b8f3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7630]
Apparently the text relocation being done here can cause runtime
performance issues. I documented a potential work-around for the
issue and provided a cross-reference link to an external site for
more general information about text relocation at runtime.
Reported-by: Laszlo Papp <lpapp@kde.org>
(From yocto-docs rev: f7f611a6668b6cd2ee3928ad44c72dbbe5307c38)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I typically try to use the underscore character to string together
multi-word user-input descriptors in examples. I fixed a bunche
here.
(From yocto-docs rev: f7bc59cfb88537a2e3045a44978e974227b8ea9f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
