The old heading was dangerously close to a heading in the
previous chapter. I altered this heading to target more
specifically the content.
(From yocto-docs rev: 797bef2256308531f02e35dc0ef8b1d9cbaff935)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to call out that using the include file is actually
using a MACHINE configuration file in this case.
(From yocto-docs rev: b33838d4711e0c55c6cf78e7491ce97bc9fd519f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This document is not a manual. We are not going to list it as
a full-blown manual. It does not need the "Manual Notes" part
in the title page.
(From yocto-docs rev: 23267dea9a90dda33d646fcfc3e8b7a1c919adea)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section briefly introduces layers but leaves the real
explanation to the section in the getting-started manual,
which this section references.
(From yocto-docs rev: 9b3957a5d7c3a2f6b41ec26205ae31f3b2d05643)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
this figure had been being referred to as the YP build process.
However, it is really more of the OpenEmbedded build system process.
Basically, what goes on during a build. I changed the way the
general figure is referred to.
(From yocto-docs rev: 1cb79b04182bd660b37637d9cec7d6edf33fc292)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is for the brief-yoctoprojectqs article.
(From yocto-docs rev: 7237c9a36e855eee9056650455a4b6f3d2412961)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have created an brief article in the form of current YP docs
that is a pared down version of the Quick Start (pre 2.5 release).
The article fills a gap for a short (2-page), process-oriented
article that steps the user through an initial build using YP.
I had to make changes to the Makefile to support building the new
article.
(From yocto-docs rev: 47aace60cea4a892ae1efabb050b240c6abdaec9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This topic was deemed unfit for concepts so I moved it to the
dev-manual and rewrote it to be "Using Virtual Providers".
(From yocto-docs rev: df7d48ac4fcf7ece75681ccf0bbb5699f7ff5ea6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided more details in the explanation and fixed a link to the
section on using virtual providers.
(From yocto-docs rev: ace74e24f001b83c9177266b0a6f15ce96dd04b0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed [YOCTO #11525]
Created a note for more explanation for how the
mount program understands the PARTUUID syntax
used with --use-uuid. Added four missing options.
(From yocto-docs rev: d8adf537d305dd55e841dd993c36ee60b5896adb)
Signed-off-by: Kristi Rifenbark <kristi@buzzcollectivemarketing.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had split up the section on x32 into a concept piece and a "how-to"
piece earlier in order to satisfy outside pressure to isolate all
"how-to" stuff in the dev-manual. Doing this put a "conceptual" blurb
about x32 in the new concepts-manual. It has been decided that x32
is not a concept. It really does not fit into the ref-manual either.
So, I have re-combined the intro blurb of the x32 stuff back as the
beginning piece of the "Usingt x32 psABI" section in the dev-manual.
(From yocto-docs rev: 6e8240cc1a90a8d78ff456d3138c525eceea3ee3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided a better flow and a bit more explanation of what Bmaptool
provides.
(From yocto-docs rev: 9a02cd7281038031fc4cdea98f114b9c318947a7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I changed the path to not list "build/" as the example assumes
the user is already in that directory.
(From yocto-docs rev: c3ab6a9e53f48005de73977238c8af3e2061db8b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Section to describe the key nature of the host development system
and its role and preparation requirements for use in the Yocto
Project development environment.
(From yocto-docs rev: 379659af343ba84f9c8fc2f47474659e06219c53)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section contains some fundamental terms people decided were
important enough to have in this getting-started manual.
(From yocto-docs rev: 42bfa0d8fc0a61c26f6b2f4b9e285c06255e8b8d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New section called "The OpenEmbedded Build System Workflow".
This section presents the tried and true flow block figure
that shows what happens when you fire off a build.
(From yocto-docs rev: 5b4313ba87a2ccd139f2b980f4cf097700421cf4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added the new section "Reference Embedded Distribution (Poky)"
section to the getting-started manual. The new section required
a new figure. I had to add the figure to the figures folder of
both the getting-started and mega-manual books. Updates to the
Makefile to include the new figure as part the tarfiles created
for each book.
(From yocto-docs rev: e5f44e17d4c1e55b6f229cc3745727e439b5bcb7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is Pock-ee with the emphasis on Pock.
(From yocto-docs rev: fd0accf40a9324060562b75ba9d3b078daf458f6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section introduces the ways a developer can use the Yocto
Project. They can use BitBake from a Linux shell, they can
got through CROPS, they can use Toaster, and they can use the
Eclipse IDE. The section overviews these possibilities.
(From yocto-docs rev: 95af6303364f94f91c94fd0bd1890b4e6351048e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New content that leverages off the same information from the new
website.
(From yocto-docs rev: 1d5bf1501a1d0efe388dc5f4a7f741a272c6301c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As glibc 2.27 can't read older locale-archives, SDKs using glibc 2.27 on hosts
using glibc earlier than 2.27 won't be able to find any locales, so bitbake
won't start and Python can't use UTF-8.
So by default install all locales into the SDK. Special-case Extensible SDKs by
installing no locales as they ship glibc in a buildtools, and that will have the
locales.
Locale installation requires cross-localedef, so add that to DEPENDS.
Also remove the explicit en_US addition in buildtools-tarball as it is now
redundant.
(From OE-Core rev: 96896568d197cd06302713c24c0f7d91bfaea6c1)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- No need to use bb.utils.which() as subprocess will search $PATH
- Clarity flow by moving the install inside the try/except
(From OE-Core rev: f4d22b7195dd8f08fe26dd353c7e860208e87d6a)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
localedef has no way to specify which locale archive to use, and the
compile-time default isn't useful as it points to the work directory.
Add support to read an environmental variable for the path, and don't fail to
write a new locale archive.
(From OE-Core rev: bf0f205a3c3714926649bd69db29e4df1c0ea112)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
nativesdk is built with a specific prefix but this will be different at install
time, however glibc hard-codes the path to locale files. Expand these strings to 4K and move them to a magic segment which we can relocate when the SDK is installed.
(From OE-Core rev: 59e0679378aac27c4fea0b06721e0a184a93c100)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The result of running dbus-test-ptest was a series of
various segfaults, interpreted as FAILs. This was a direct consequence
of the test suite loading the installed shared library libdbus-1.so, not the
one built along the test suite.
While we normally want to test against the installed libraries, we cannot
do this in this case as the test suite expects a library that is configured/compiled
differently from the installed one. We could configure the installed library
identically as the test suite expects, (and there should be no issues), however
this is not desirable for performance reasons.
Hence we need to use the library built along with the test suite.
Of course, running the test suite against its own library does not
test the installed library, however they are both built from the same
sources so that can give us some kind of indication.
The following changes were made:
1. Configure the test library as close as possible to the installed one,
with some additional configuration options that are needed for testing.
(Use dbus_1.12.2.bb recipe as a template)
2. Include the shared libraries in the package, use LD_LIBRARY_PATH during
testing to load them instead of the installed ones.
3. Add a few more tests. (There are still some additional tests built that
are not used, but they would have to be special-cased).
4. When evaluating the test results, differentiate between "FAIL" and "SKIP"
[YOCTO #10841]
[YOCTO #12277]
(From OE-Core rev: 5d148aa9c3c338fabab1e60e2ca64d09c9b8477f)
(From OE-Core rev: 0828850fd09f738572ae8259384af07eeb81182b)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The shlibs detection/handling iterates the package list twice, but PRIVATE_LIBS
is only fetched in the first loop which means the second loop only considers the
value set.
(From OE-Core rev: 8c90c0081c38b33c99655f806cbe668600c170cc)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If a standalone tasks adds a dependency on X:do_build, the code in runqueue would
currently remove it if that do_build was part of an image recipe which uses
recrdeptask on do_build.
Such individual tasks shouldn't do this, therefore tweak the recursive reference code
to only process recurseive tasks, not all tasks.
(Bitbake rev: 4cfca360891e1ed876a9c19487b4f6210686af26)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recipe depends on many machine specific tasks and should be marked
as machine specific itself. This fixes signature tests after some dependency
issues were fixed at the bitbake level which exposed that issue.
(From OE-Core rev: 4889704fed9ec205eb964b9e8ee7ff384e5c741d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
