Note mentions possible differences between docs in the released
tarball and docs on the website. Suggests website for latest
docs.
(From yocto-docs rev: 92eb8221bdaee94b3d5861b929ef1adb986cc865)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Note mentions possible differences between docs in the released
tarball and docs on the website. Suggests website for latest
docs.
(From yocto-docs rev: 1b729667498363a5bb451502975b0797796eea0b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Note mentions possible differences between docs in the released
tarball and docs on the website. Suggests website for latest
docs.
(From yocto-docs rev: 29426ab131a319b764f82da8a11cb4d9b590c3b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Put the note about manual differences in the legalnotice area.
this produced a better looking note.
(From yocto-docs rev: 8d44a5fba7c52d5798758467e93c9c64e48d512a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Note mentions possible differences between docs in the released
tarball and docs on the website. Suggests website for latest
docs.
(From yocto-docs rev: 1675c31aa02a4daed356af4ea9c78d493a9a2597)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the BSP flow illustration.
(From yocto-docs rev: 82ec8528c058d702402767ffa471695eb82e259c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In dev-manual-model.xml I included two references: one to the
BSP Development Example and one to the Kernel Modification Example.
I had to add the target "id" stuff to both dev-manual-bsp-appendix.xml
and dev-manual-model.xml
(From yocto-docs rev: bcae1e723610e1769f0a524e3c1d9918c7cb1061)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No need for this chapter any longer. Re-org has ash-canned it.
(From yocto-docs rev: 085a514133f4326c1da372b95507a3665e8f91ed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I removed the cases chapter and added an appendix for kernel example.
(From yocto-docs rev: 60c8ec3444c08e94468ff349b676652c7f6ff0cd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the Docbook tags to make this an appendix.
(From yocto-docs rev: fd5658872a9d48a2ee8f0229cb0fca90961aee32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New file for the kernel example. this will be an appendix.
(From yocto-docs rev: fca7e4fbb3d1e738700349d6169d7217c04e4b31)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
this is now in the model chapter. Eventually the cases chapter
will disappear.
(From yocto-docs rev: fde20eede9f04899b61742b05ce73c97b2737bf3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added structure to contain sub-sections for system (BSP and kernel)
and application overviews.
(From yocto-docs rev: 028f65219b001081d221d63f368ff06066a95a64)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "models" chapter is going to be the overview section for the cases.
Thus, the cases chapter will disappear. This is a first step in that
direction.
(From yocto-docs rev: fe3985db8e1dbc7bff6565d3624bccac0f809621)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some of the more general BSP development information was more appropriate
in the dev-manual-cases chapter. I removed this information and left
example-specific (mostly) text.
(From yocto-docs rev: d44c0fa8bdea9a2cad51ae3ca4b861a12d9fcdf9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Because the BSP example is now in an appendix, I re-wrote this section
to overview the case.
(From yocto-docs rev: c0d88c6050bd17d65d8fe8c8abb227998fd4c11e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section for changing the recipes was deep and complex. So I broke
it into several sub-sections.
(From yocto-docs rev: f964b7644502fe5995c57de4a7a4fff47f71cf79)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I re-wrote the Getting your Base BSP section to reflect the example only.
Previously, there was a lot of information in there about getting BSP
files that was deemed universal and was moved to the getting started
chapter.
(From yocto-docs rev: addcbca37e3dfad27b388245a4085cd0a2747177)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the YP BSP naming scheme to the general getting started section
where it talks about getting BSP files on the local system.
(From yocto-docs rev: 5b8dc20a52053341ac726fe6662152397262d5e8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I moved the example for setting up meta-intel into the getting started
section. This information is universal and needs to be isolated.
(From yocto-docs rev: d43ecd16a95fa53cafa09e933c67cacd85227021)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I moved the section that provides the universal methods of getting a local
version of the Yocto Project files and BSP files on the development system
into this section. this information needs to be referenced throughout
examples so it should be in one location.
(From yocto-docs rev: 718ea5b468d816ea4f61a6ffa4de7db396fe3ed4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed the spacing to follow my indentation scheme for Docbook files.
(From yocto-docs rev: 6ed8cbc7dc48e5a380d27ee280fb92809b931223)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
added the start of the kernel example. It is not complete.
There are other various edits made throughout the chapter as well.
(From yocto-docs rev: 39ba857b71aa643593a539d979186753fb7a9049)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the list of files to include dev-manual-cases-bsp-appendix.
(From yocto-docs rev: 0756e69e25fb4008fae592f3e06b03b3d773e0a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I decided to take the long detailed example of the BSP creation and
make it an appendix. This commit represents a simple copy of the existing
dev-manual-cases chapter. Further commits will change the text to
make it suitable as an appendix.
(From yocto-docs rev: 8c1308c4361f48ce7f7aa104cde7e6f6a820faa4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Completed the terminology scrub for the yp files.
(From yocto-docs rev: c99f64541bf09ad7267625828894e3364dcdf937)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made a pass through the chapter to try and lessen the confusion over
yp files in a git repo verses those unpacked from a tarball. Also
tried to write the example for the 1.1 release but I don't have the
real software yet and can't supply actual names of files.
(From yocto-docs rev: 2ad973bd1f17005a3922651060d025795634d222)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
General edits to the workflow section. Also created a link to
to Bugzilla in the next section.
(From yocto-docs rev: 2e70b19d24bb4649fb525232fca9ab2e01c5ec61)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
created a new section on YP terms that might be useful to the new user.
(From yocto-docs rev: ab81b6468c39b5c015c7c0654ddf8c4cfd8bd245)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I re-wrote the source repositories section a bit to better reflect the
overall picture of how the user finds and decides on source for YP.
Also added some punctuation to the licensing section.
(From yocto-docs rev: 12ec18e58eb4e4dc395c2161908a60d395684ab3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have a new understanding of the files resulting from setting up
Git repos as compared to getting files from tarballs. I changed
some wordings to help make those distinctions.
(From yocto-docs rev: b7ba9df07cf9d64f61ac73e501c253c42570970d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed "complete reference guide" to "a reference guide."
I don't really believe the Poky Reference Manual will ever really
be complete.
(From yocto-docs rev: 9afcfe03e4f3595ac78f2cda111e5bd025654595)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These converted it to 1.1_M2. there were a lot of changes going from
the original example that used to bernard to 1.1_M2.
(From yocto-docs rev: c5dbc8da1ebc0b710e8133fcdd5893e33776148d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Partial stuff as I am working through the BSP example trying to
use git clone instead of git init per Darren Hart's suggestion.
(From yocto-docs rev: e829d761575786093c9ac1f1b901a2151011ce9d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Initial content in and the formatting complete. Some bad links fixed
also.
(From yocto-docs rev: 2461522b77c8240476a14aef8f3e94336419af56)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three issues pointed out by Robert P. J. Day.
1) Missing text for "This optional GNOME mobile-based UI, which is intended for
devices with resolution but restricted size screens ..." I re-wrote this
so it makes sense.
2) Scrubbed document for incorrect usage of openSUSE. There were three
occurences.
3) Made several changes to the example of using a pre-built image. The
arguments to the poky-qemu command did not exist (they were old). I
used existing arguments now and I also bolstered up the root filesystem
explanation a bit.
(From yocto-docs rev: 31b7a97dfd11ff50ee6c554bf8647591021fef72)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Syntax did not have line-continuation characters in the zypper
example. Error found by Robert P. J. Day.
(From yocto-docs rev: 4ecbd3d1706336ddc691bf4ce6763a179f3f70a6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the initial content for the chapter. Previous content was just
copied from an adt-manual chapter.
(From yocto-docs rev: 145fdacb2d080b97dc033f677fccb4fa5ab8e5d3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the dev-manual-model.xml chapter to the list of chapters
to include.
(From yocto-docs rev: 513faf68cdf338b28020119266148287ea459916)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This version of the content is a placeholder only.
(From yocto-docs rev: 3c896a95f2d6593ef8af3d90829611122bef9aae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This content is the first cut for the chapter. The original was a copy
of some adt-manual chapter.
(From yocto-docs rev: 4a563c3ed1e82837410ed114a07e39a0ccaad6f7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The original content of this chapter was simply a copy of an existing
adt-manual file. I have added the content for the chapter.
(From yocto-docs rev: cac53540d8449f605ab40775c317b613711f3a80)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New content from my working chapter. Previously this file was just a
copy of one of the adt-manual chapters.
(From yocto-docs rev: a50e69c19c23808d44ac4448b30394eedbbdbdab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
the make was failing due to me not following a naming convention.
I renamed all the files so they have a pre-fix of 'dev-manual' and
then deleted the old files that had a pre-fix of 'dev-man'.
(From yocto-docs rev: a4157ece0d994d5f269c94fce71c0b598bfd6a9e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Toolchain filenames corrected. Discovered by Robert P. J. Day.
(From yocto-docs rev: 3afa1d71be04c6aedafe952855a23ccbd3547b68)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Was suggested that toolchains "should" be installed under /opt/poky.
This is in fact a requirement. I replaced "should" with "must."
(From yocto-docs rev: fe890b056831a84cde47f9200300491426f20c65)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Copied from existing book and title changed.
(From yocto-docs rev: d522d738f527aac5449c7d7b60dd457c0e912c3e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The example bitbake command now has the target core-image-sato.
This reflects post-bernard.
(From yocto-docs rev: 3ff1ee07947f301c4df2a9aea8d1aab15c5237eb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
changed 'meta/recipes-kernel/kernel' to 'meta/recipes-kernel/linux'
as the location for existing YP kernels found in the repository.
(From yocto-docs rev: c8ce3a15429df5c980498ce217803cf5a59cbdc9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added text to help put tree construction into context with the developer.
The section felt as if the developer needed to be taking action on the steps
when in reality the steps are describing a lot of "behind-the-scenes" stuff
that happens when the YP tree is constructed.
(From yocto-docs rev: 1aafca94f3f3d5e07a0b2244ff5dbfe4a2c1ba8f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a sentence clarifying the intended audience of this chapter. It is
specifically for developers that want to modify the YP kernel and contribute
changes upstream to YP.
(From yocto-docs rev: 1012dcb8312cb83fe64397742142071f20ae4e24)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Cleaned up the list construction.
(From yocto-docs rev: 29dd0a40bf9844de631941b7f26d1181fd17c95b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section has been re-written to just include high-level overview of the
steps. The detailed example that used to be the section is not needed as
there is adequate documentation of this process in the Yocto Project
Development Manual and on the wiki courtesy of Tom Zanussi.
(From yocto-docs rev: 7355734a5ed965401027ba23bfb15fd926a171f7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I forgot the 'git' part of the 'git push' command for the fix requested by
Robert P. J. Day.
(From yocto-docs rev: 458e18bd9d33c12ff3367cae8a4cc0c6c640b932)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes requested by Robert P. J. Day at rpjday@crashcourse.ca to add
a missing system prompt character and fix an overly long git push example.
(From yocto-docs rev: 71ac0b23682c6a405ae454cab02120993d2f370e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a partial edit of re-writing the BSP creation section so that
it is clearer for the naive user. It is not quite done yet.
(From yocto-docs rev: 7a552e72a1d2d1b6ffa93f4fe3074f318ff35715)
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>
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>
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>
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>
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 #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>
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>
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>
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>
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>
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>