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: 9aec91d7f4fda558baa0e8a0290b42d76e735c63)
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: e1ab48f7def9d1eb080e007b88f75172470b8007)
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: 3d85d5385c03841c17dd33afb94c110edc12170f)
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: f8dccf3f115647cb039d91415819186cf38fa8bb)
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: 20eafc8290f46d8deea84dd6ff721b65cb8a1463)
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: d8a7e3443d33d02d88e9d603dcff917a5508ae17)
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: 447ad6167570bf1bd227771153de421d1154443d)
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: 519d0ff95e2ffbdb615d6dc27a6c11b393eb4b53)
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: f825ba932970e9d62d335f249365a34b2992b6cd)
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: b63ec6c706f41dc4666c2fd79d797962c35f8baa)
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: ea33b98c0a7ceb80adb15bf63eee8d6872099235)
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: e8742267506bf9359346cfcd3965f762ed2c7d6f)
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: ec79c9a39955b22cb2b8cec44ffcaab22aba479b)
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: ef6dbf591eee70866f163e3c98454b6145f4fa3a)
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: 09e67479f470ca4b21f532c5fc96f36d3bf1a39d)
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: 68474b5a8b5c96b0fc19fda29e667369f4606e31)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the introduction, the ref-manual references several other YP
manuals. If the manual is build separately, these references resolve
to the appropriate manuals. When the mega-manual is built, the
same references are designed to not become links. In otherwords,
mega-manual.sed processes those links out. This is by design.
I found a #profile-manual tag on one of the links in the introduction.
This resulted in a link in the mega-manual that would go nowhere. I
removed the tag.
(From yocto-docs rev: fdaf114ece20994ec55061612ab53e9334afde26)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A link was going to an old YP page that talked about patch
style guide stuff. That page simply redirects the user to a
styleguide of the OE. I fixed the link in the manual to go
directly to that page now.
(From yocto-docs rev: 913c30eae42e89cc6f8dd99026594c2843985c58)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found a link that is processed by the mega-manual.sed file correctly
but for the situation it does not resolve right. The link is a
"naked" link. In other words, it doesn't have a #<tag> part.
When the .sed file sees these types of links, no hyperlink is
generated. I found a case in the dev-manual where I reference the
Toaster Manual in general and would like a link that would take the
user there. So, I had to add a #<tag> part to the link in the XML
(From yocto-docs rev: ab11e9822b5ec1b0f7138f1419ce9c340f6f27ad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I put this in the intro list for the section that presents various
ways to use YP.
(From yocto-docs rev: 05f924f799a1f1396bf7154b298aabc3d06ad1d7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This practice is not good. I had one in the manual. I reworded
the text to not use that term in a link.
(From yocto-docs rev: 53636ae7370827945b31d11785410dd44670bb91)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Repositories, Tags, and Branches" section had some wording
that described how branches are maintained in the poky repo that
made it hard to maintain in the doc from release to release. I had
a list of past releases by name and as such would have to update
it every release to make it reflect the last set. Well... this
is not the best way to do this and proved out as it slipped through
the cracks for the YP 1.8 release. Consequently, I recast the text
so it is "release proof".
(From yocto-docs rev: b6e27d06df58a43bb767e9616ccf3c0711e83cf6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In an attempt to keep the project as much open source as possible,
I removed the link to Intel from this list of resources. We don't
list Linux, OpenedHand, Wind River, etc.
(From yocto-docs rev: 5efe375a94a14d4a70aa2c3ff9ab39d6c7362526)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some stuff about "poky" meaning the default distribution
when using YP and the poky git repository to build an image.
(From yocto-docs rev: bd534a5bdf405044c8f1a60ee9e251bff2a0e53c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The send-error-report tool syntax has slightly changed since the
documentation was written. Removed the [server] part of the
command and added more detail on its use and results.
Reported-by: Michael Wood <michael.g.wood@intel.com>
(From yocto-docs rev: 10e28ab877b327301be536e5d515d5a419d082ac)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Wic is not using parted and other runtime dependencies from host
system anymore. It uses native tools instead. Removed host parted
from the list of requirements. Added instructions to build native
tools.
(From yocto-docs rev: ab22aff62bd9ffde3dfefe9fcabadc6e5aae7e31)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
An old note still existed in this entry that stated we don't support
glibc. This is not true. I deleted the note.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: e72f248f45678fb445e60106dd338c4d9cd114d8)
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: f7ba2fd03ee40c5dbe6a07a24a63d9147857ed78)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Style sheet was not spacing after the first paragraph for glossary
entries.
(From yocto-docs rev: fb08aec5303ed21315839c55b413873569497f23)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This involves the following:
* Inserting a new row for all manual revision history tables
to have "October 2015" and 1.9 as the release information.
* Updating the mega-manual.sed file to process links for 1.9
* Updating variables in poky.ent to deal with the 1.9 release
variables.
(From yocto-docs rev: 1ed55c08b96cf0fded38833635111a5c6da86781)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7133]
Added more examples of how variables work in Makefile projects.
(From yocto-docs rev: e8aa42f3609de3dfe94c022d957b855a4f7ef032)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7559]
Added some explanation on the syntax. As it was, the positionally
dependent nature of the script's parameters was not accounted
for. This is now explained. Also, talked a bit about the
bitbake-cookerdaemon.log file.
(From yocto-docs rev: fcf52a15acea2d75df9c84550d7e73c988ffb4bb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A cut-and-paste error had left a "package_deb" string in the
first sentence of the section. Replaced with "package_rpm."
Reported-by: Geoffroy VanCutsem <geoffroy.vancutsem@intel.com>
(From yocto-docs rev: 38b20d775ba41cb14d86177dddd85ada32fb3f86)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
