| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
(From yocto-docs rev: 564a28c2501034ea7e2eb16afc43dfaf931b6f6f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
We haven't supported ipkg for some time now - it was replaced by opkg
(whilst still using the ipk package format).
(From yocto-docs rev: 07b3dd9a73be25f31c919ed750ca320c7507eff0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently. The faq entry changed is
"How does Poky differ from OpenEmbedded?"
(From yocto-docs rev: ecc88ef12ec2faa48d05824e8b781a7d43e86127)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
The entry for the question "Are there any products using
the OpenEmbedded build system (poky)?" was updated. The
changes result in a better question and answer.
(From yocto-docs rev: cfc4a945738e891d20ab1a2a7002c5c421b0a225)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Explain that we test with a set of reference hardware rather than only
supporting hardware that we have (avoiding any implication that the
build system can't support other devices). These are in the
faq entry in the poky-ref-manual for the question of how we can
claim Poky / OpenEmbedded-Core is stable.
* Adjust the language so that it is OE-Core friendly, with a link to
the Development Manual for the definition of OE-Core.
(From yocto-docs rev: 5ff1604dd383b26e918c319fcbe46dd1589cebc5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Since we are using a layer-based approach, people do not
need to rely upon the Yocto Project team to add support
for new boards.
(From yocto-docs rev: 569ff9da7443f9654f288d0a4e62ef06ba34ba52)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From yocto-docs rev: d0b2b7983fb3d6dbd9525a094a72573b62a8d276)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
Took out the FAQ question about using Ubuntu Intrepid and
seeing build failures.
(From yocto-docs rev: 2885aa27904d4b31541f77ceeb54ad94a8e21378)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the decision to create a single HTML file that has all
individual YP manuals, the need for including the BSP guide as
part of the YP Reference Manual goes away. I have removed this
guide as a chapter, removed the mention of it in the introduction,
and fixed the two links in the FAQ chapter to reference the external
manual.
(From yocto-docs rev: b0dbda9e09b73c2b26111bda118731dbb3090cae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "faq" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
(From yocto-docs rev: 6e090132823e3b121d00d9116b0693c922156b32)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
Updated the FAQ entry on "How do I use an external toolchain."
Comments were from Richard Purdie.
(From yocto-docs rev: db3986d2eff17087eb141ac0f4dfed55ff753368)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
Found a stray reference to "Yocto Project Build Directory." I changed
to "build directory."
(From yocto-docs rev: e0c593ac162c61f7d42625482b95c253d0f8622a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
I have changed as many "Yocto Project" terms as possible so that
better reflect reality.
(From yocto-docs rev: 5f729e53b0cb653c97621e4e6598d9295d60ada5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new FAQ entry on how to get rid of build output and
start over. Sourced by Robert P. J. Day.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 3b94911aaf64b9618f8dbc0d8b98384b9ebd33b4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
I have cleaned up a bit of the FAQ entry for how to use an
external toolchain. This is not complete yet.
(From yocto-docs rev: 030324a6881d8b9b0bcf476a2b7bfdd6fbd978a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Reading through the manual I discovered some inconsistencies with
how links were handled. I fixed this in both the QS and one anchor
in the FAQ appendix of the YP Reference Manual.
(From yocto-docs rev: 32444e839a1541ab2c02fa31cd094605d1a2429a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some instances in the manual where it was not clear on whether
the subject was a shell environment variable or a BitBake
environment variable. I cleared these up.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 123bb91a3954c98378cdd8bba0a35311eb53f37a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
Fixed all the hard links to use appropriate variables from the
file poky.ent.
(From yocto-docs rev: 9a6267d0d843dc47c1171eba6200387901b77df4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From yocto-docs rev: 8e861c6fc07aefa81ff65e3542de855116e14969)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pulling the "Common Tasks" chapter fromt YP Reference Manual
broke many links. Each of these links had to be repaired so that
the link is to the YP Develepment Manual now, where the chapter
was moved to.
(From yocto-docs rev: 08176135b8ac856b8cf7872300ce41ada87fa486)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The information surrounding the central download directory was
pretty scant. Jim Abernathy pointed this out in an email sent to
me. As a start, I have added quite a bit more information to
the glossary description for DL_DIR. Part of that added information
is a pointer to the FAQ entry that describes exactly how the
build system gets source files. Then, in the YP Development Manual
in the section that introduces the build process, I added several
references to various variables that are set in the local.conf
file prior to kicking off the build.
Reported-by: Jim Abernathy <jim.abernathy@intel.com>
(From yocto-docs rev: 4d7835a3bff5bd054301fa9ab6954c11c88dad58)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
The links to the 32-bit and 64-bit Python tarballs in
miscsupport were broken. I fixed them.
(From yocto-docs rev: cc50d1ea3155cf1dd8d060c2c361b99b4f7d0d8e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
After greping through the documentation directory, I addressed
all the <ulink> statements that used to have yocto-1.0 in the URL.
They are now yocto-1.1.
(From yocto-docs rev: 97d160263c5905fdeaf4ec285bc5359918790581)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per Paul Eggleton he suggested that the wording we had about YP focusing
on the GNOME Mobile environment was misleading now. It was in there in the
original version of the FAQ but with time has become outdated. I simply
removed the "GNOME" part and left the part that mentions about YP
being a stable
environment and well-suited for the embedded mobile environment.
(From yocto-docs rev: cc7103eda3fd77d89cecfffa23f0f798aa512132)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In general, the term Poky can be replaced by "the Yocto Project."
The term Poky can be used as a term for the Yocto Project build system.
I left it in place for a few areas where it was easy and would not
be confusing.
I also performed general rewrites for the FAQ.
(From yocto-docs rev: bb24bcf21311c68576fb8c3fec86ad8303f557f2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From yocto-docs rev: 089575ceb618199fbeccad1a4e7b7bd19eb5ad7f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
| |
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
(From yocto-docs rev: a5b069b04979a566b08415cf27af2ad6abf90f2f)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
This is an explanation on how to get by the proxy or around the
firewall when Poky is trying to find and download sources.
(From OE-Core rev: 426df8458bb37c81afc6fe03f0e1300985c8d059)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added three FAQ entries per Joshual Lock.
1. How do I disable the cursor on my touchscreen device?
2. How do I make sure connected network interfaces are brought
up by default.
3. How do I create images with more free space?
(From OE-Core rev: 9cfed91ee7c0a619e52abc098c20d6ed8b69416b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
| |
Performed a spell check and corrected several problems.
(From OE-Core rev: e26e9f41eac1bb34a7d9276921d14e843444622d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[BUGID# 553] - In the FAQ appendix item H.12 there was a reference
to http://pokylinux.org/sources/* in the question portion. The
reference should really be http://autobuilder.yoctoproject.org/sources/*.
I made the change.
This is a partial fix for bug 553.
(From OE-Core rev: fb56ac6021fe09cb386c168f3fe0b11e04214972)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
| |
Python 2.6 requirement.
As part of the fix for #628 I added a new question to the FAQ for use
of Poky when you do not have Python 2.6.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|