| Age | Commit message (Collapse) | Author |
|---|
|
yocto-docs rev: b32290b381a6ed2cbfe3e01b748c794ef6bc876b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
yocto-docs rev: c79d17e29d5690a8df9943836286232cd3aa8893)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
yocto-docs rev: c83d92d99bc1104169a06623c787b07a9d199039)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The "Poky Tree Mode" has been replaced with "Build System Derived
Toolchain". SDK Root Mode has been replaced with Stand-alone
Prebuilt Toolchain.
(From yocto-docs rev: 453f7c030e6d7625d382563e2f2ec569f76e95eb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: b8f314fb3dc638c85bc9f860fb591ee3a8dad614)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Used clearer wording.
(From yocto-docs rev: faa35ea8cdb1747ba2b6b7717d1881830bed175b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updated wording to reflect proper use of build tree terminology.
(From yocto-docs rev: 82b47279b55b6d15bf260e0903505fe578c985c9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: 14173522e5d6d219c336d6dafafcb7d1c734c584)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
yocto-docs rev: 0f052154a4c7456bf10a7151bd3d4e70f51be1b3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
changed the wording for installing required Eclipse Plug-ins.
It was confusing.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Changed the command examples so the variables contained underscore
characters.
(From yocto-docs rev: 34bfceb14a04c5fa026486f33d32df7c21f8c742)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Armed with a better understanding of sysroot I made some edits to
help better define what is going on with the various sysroot
variables in the adt installer configuration file.
(From yocto-docs rev: 2b63e1f0f57c701eb38de7f9b9057567786b9899)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Small correction to refer to sysroot instead of root filesystem
in opening paragraph.
(From yocto-docs rev: e9af5bbd69ab9421a97ce87d5210d31838e93151)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The note indicating where you can get sample kernels and
filesystems suitable for QEMU had a wrong path. I added
"machines" to the path. Also made a wording change.
(From yocto-docs rev: 75261eb7a44dcc990a817b5b59323042c38b6839)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The example command I used to setup the cross-toolchain environment
was incorrect. I added the "1.0" to it.
(From yocto-docs rev: b8bb60ec69296e9c927735f3fca86013e8b2624e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Significant re-write to every section in this chapter except the
"Setting Up the Environment" and "Kernels and Filesystem Images"
chapters. I established some terms to communicate the build and
source trees and the build and source top-level directories for
YP. These terms had not been consitently communicated. I also
stepped through each of the three methods by which a user can
install ADT (and the cross-toolchain) and meticulously documented
the steps. The result is a much more complete and clear set
of procedures.
(From yocto-docs rev: 37076a07ccc748ceb416c4bc3a57b698f6e8d80a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From yocto-docs rev: 1ea4683eb41e4be334b053c622ed5bf08041d617)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I provided more detail in the section that introduces QEMU and tells
how it is made available to the user.
(From yocto-docs rev: 9145fee2d550af57669120b1b413585b69ab14bc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
rev: 738c4f25ba6bcc408789dda118b127d716c2f4c6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The manual previously defined the "ADT" as the toolchain, the sysroot,
QEMU, and user-space tools. This definition was creating some confusion
when it came to installing the "ADT". Namely, some of the items you
don't even install, such as the user-space tools. So I recast the
definition of ADT to mean the cross-toolchain and sysroot. I cast the
other items as part of the overall development environment.
(From yocto-docs rev: 6ee891660d3b6bf6e2a3f4b5a872ade7a007ce02)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Turns out that the package libtool is necessary for working with ADT during
the installation process. I need to mention this in the ADT manual but
it would be helpful if it was one of the packages in the QS along with
all the others. I added libtool to the package requirements lists
for the three supported hosts.
(From yocto-docs rev: 5f95fa1af0cfe9a97e437b8239e139479a1d5317)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Partial commit for supported distribution change.
(From yocto-docs rev: 4a84894dc2964f0153294b87f6205c432a482ac2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I included a new note to help users of pre-15 release Fedora enable sudo.
Along with this I repositioned the note about using non-supported
distros into the main text. Overall the section includes more information
and is organized a bit better.
(From yocto-docs rev: b0ae94b97ae46562ddde79df83462adf88b94527)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I updated the packages section to also include the zypper command
and supporting commands so that the OpenSUSE user can install
packages.
(From yocto-docs rev: 3a9a0f7fb03bf264e1587d181db111a542e7964d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Added text suggesting that BB_NUMBER_THREADS be set to twice the number
of available processor cores and that PARALLEL_MAKE be set equal to the
number of processor cores. Similar changes were made to local.conf
based on work by Josh.
(From yocto-docs rev: e342a4af4d3ba000b348bbb9d125977fc0e95273)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the note that tells users YP must have Python 2.6 I added Python
2.7.
(From yocto-docs rev: 611ad6331a8b3e1acc98f2029a181a92f32220e0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The entry previously stated that only Python 2.6 is required. I
added Python 2.7 to that requirement. I also changed the URLs that
point to our pre-built tarballs from which the user can get Python
2.6 to be in the yocto-1.0 download area. They were pointing to
an area in the index of downloads that was up one level. According
to Beth the official location is
http://autobuilder.yoctoproject.org/downloads/miscsupport/yocto-1.0- \
python-nativesdk.
(From yocto-docs rev: f5ba36dee8094209fa6d3c6f97656588ded0567f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
yocto-docs rev: b2f45f73832a2289158bfb89313957a48dded1cd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
YOCTO #1104: The section that describes how to customize images
with new features failed to mention the variable EXTRA_IMAGE_FEATURES.
I added text to include that option and referenced the variable.
(From yocto-docs rev: 128b53594be02e486ca3f4658b9f93b9913a3972)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
EXTRA_IMAGE_FEATURES
YOCTO #1104: The section describing the local configiuration file
local.conf lists out variables used. One variable it had in there
was IMAGE_FEATURES. This variable is not in local.conf. But,
EXTRA_IMAGE_FEATURES is the variable that is there. I corrected this.
(From yocto-docs rev: 2698d0fc61adc8971a84436529a54190c998d4d6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The Images reference section states you can control what features are
in an image by using the IMAGE_FEATURES variable. It failed to mention
the EXTRA_IMAGE_FEATURES variable. I included this variable in the
discussion.
(From yocto-docs rev: 6c7789bd409f43a3978c09c43db31010bc461573)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
EXTRA_IMAGE_FEATURES
Added a cross-reference to the EXTRA_IMAGE_VARIABLES glossary
term and provided more explanation describing the relationship
between the variable and the IMAGE_FEATURES variable.
(From yocto-docs rev: 227c11b8d81e9ae266b7e60172d0a5e9e1237ed0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
EXTRA_IMAGE_FEATURES
YOCTO #1104 - Added a glossary entry for the EXTRA_IMAGE_FEATURES
variable.
(From yocto-docs rev: f81a85322d944d33484da73020593891811a045a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Removed several instances to the 5.0 Bernard release. I replaced
these with the 5.0.1 release. I also re-wrote a paragraph that
instructs the user on where to find and download the most recent
YP tarball. It used to point to the Index of /Downloads into the
"yocto-1.0" folder. I now instruct the user to go to the
Yocto Project website and download the desired release from there.
(From yocto-docs rev: 30b5163730139b2b852d64c87a7e710b7fcc7dad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I added an entry to represent the Yocto Project 1.0.1 Release into
the manual history table for all of the manuals except the Yocto
Project Quick Start, which does not have a table.
(From yocto-docs rev: d2c570b18854b3f15dfb20436a2212f569e96d5f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
[BUGID#_1025] - I added some conditionals to handle the
Yocto Project Quick Start case. This manual does not have
a PDF version. I put in tests for publishing and for a case
where a user might attempt to specifically generate a PDF
using 'make pdf'. I also converted the version variable into
a command-line argument so we don't have to edit the make file
when a new release comes out.
(From yocto-docs rev: 8e98871c9771096ec635f592cca752c63697bd5e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There was some URL problems with the publish statement.
Beth debugged it.
(From yocto-docs rev: 6c13bce3cbdd576463f5e3b1e61ab6f4046e47c3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
These changes fix the following issues:
1. Multiple Makefiles. There really is no need for this.
2. Unable to maintain more than one version of the docs on the webserver.
This is a quick fix to enable the above.
In order to build the documentation, at the top level, issue a:
make all DOC=<doc directory name>
make all DOC=kernel-manual
Also, some changes need to occur on the webserver to fully
incorporate these fixes.
http://www.yoctoproject.org/documentation/
The docs are now published to:
http://www.yoctoproject.org/docs/<Release MM.mm>/<doc name>
The main page should be changed to point not only to the current doc release,
but also to the prior releases. This will enable us to maintain prior release
documentation without stomping over it when we publish new docs. Also, we'll
need to repoint the yocto-quick-start link to yocto-project-qs. Or rename
documentation/yocto-project-qs/* to support the website naming.
(From yocto-docs rev: 2651790d80fd32cd4619eeb5375f6ee28e7e7fda)
Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Added a new FAQ entry per Richard Purdie answering the question
'How do I use an external toolchain?'
(From yocto-docs rev: 58b78df0d78637234cbcb0e70e225b72ba0f9a2b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
poky-qemu
Evidently the command 'runqemu' is not a valid command for Bernard.
I changed four occurances of 'runqemu' to 'poky-qemu'.
(From yocto-docs rev: 0296920cc07a6fb9871c5af4bb991fcee2949564)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the example for building an image the command
'source poky-bernard-5.0/oe-init-build-env poky-5.0-build' was used.
Torsten Scheck notified Jeff Osier-mixon and sent the fix to
change to 'source poky-bernard-5.0/poky-init-build-env poky-5.0-build'
I made the change.
(From yocto-docs rev: b96646efb203e482d53d922fb120672df5a09966)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
option
BUGID#_1083 - I added the -k option as part of the bitbake command in the
example that builds an image. I did not explain it as that is beyond
the scope of the quickstart. I did however point the user to where
they can find information on it.
(From yocto-docs rev: 620351d38c67ff14cefc7a52bbc0e98789011677)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the section 2.1.1 BitBake I added a paragraph at the end of the discussion
about BitBake explaining the benefits of the '-k' and '--continue' options.
(From yocto-docs rev: 409e01cedbe8d93c29856fa2a49d5f9db91f5201)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Added more explanation about the base directory (meta-<bsp_name>) to the
Example Filesystem Layout section. These changes were suggested by
Tom Zanussi to help users understand better how to add BSP layers
to the build system.
(From yocto-docs rev: ced445910363b2f10b5b5ca72236f54ae4b7e050)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Added a new entry for we do not support spaces in filenames.
This entry was suggested by Richard.
(From yocto-docs rev: 27d7f951056fb55bddcd7a71374359583c635073)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the 'BSP Click-Through Licensing Procedure' section there was an
old link to the BSP download page on the Yocto Project website. The
link was non-functional. I fixed the link so that it points to the
Yocto Project BSP Download page. I also re-wrote the paragraph to
read better.
(From yocto-docs rev: b87714fa54f71aa061126b7f29d80723a90818e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the '1.1.3 Pre-built User Binaries' section it said that the
ADT and minimal images were kept in the optional
meta-<bsp_name>/binary directory. Jianjun Xu pointed out that
in fact it is just the minimal and sato images here. I also
confirmed with Tom as well. I re-wrote this sentence to be
clearer and more accurate.
(From yocto-docs rev: 6757abff52841b5d1e1991ab22314fa7a243a87d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In the '1.1.4 Layer Configuration File' section there was a BBFILES
statment that used the '\' character to indicate a continuation of the
command on the following line. However, the example did not use
a new line. I added the hard-return to correct that in the example.
(From yocto-docs rev: 185352ae2f5879a8418715053f3791b167bd6d7e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Changed the example BSP name 'meta-intel_n450' to 'meta-n450' in
the section 'Example Filesystem Layout.' Error found by Jiajun Xu.
(From yocto-docs rev: 0dd6f97dcc51cec4bae96ca0430af9300619749f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There is a newer version of the yocto-environment.png file that has
OE-branding. This is the figure used now.
(From yocto-docs rev: 094c0c9661ec1c00da2a1fd0ab4818c0075a8b52)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
Scott Rifenbark
Beth Flanagan