There was inconsistent use of the way directory names were
handled throughout the YP documentation. I have scrubbed the
set and replaced many instances such as the following:
meta/<something> replaces /meta/<something>
poky replaces ~/poky (except in some very specific examples)
I basically got rid of leading slash characters.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: ae2e451ed8f61484d04b30017021912c4493a441)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Significant tweaks:
* removal of (confusing) leading slashes from YP filenames
* deletion of reference to non-existent "build/tmp/pkgdata/"
(From yocto-docs rev: c105ae9c6741fbe195addf52d313925bab50ba40)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This folder disappeared and I was not told about it.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: d2526d773d282cf81e81f60745a47fbdc9625254)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added more wording to clearly state what is going on when you
run this script.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 2b23966d80b2787f7eddcbf6c635220d58d7a494)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I altered three areas from the previous patch submitted and
applied from Robert P. J. Day. Two minor wording changes and
removal of negative language.
(From yocto-docs rev: 0212b01f82637c3498f26bce57e98508c84799c5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert P. J. Day noted that the bitbake command no longer uses
a wrapper as the section indicated. I have removed this reference.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a523d4d4fc57edabfa4aa7d20e154cdc43d35fca)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was some confusion over some things in these two sections.
I re-wrote them with the help of Paul Eggleton to be clear on
them.
Reported-by: Robert P. J. Day (rpjday@crashcourse.ca>
(From yocto-docs rev: ab352523e82626d8356d8b2c07fb10d2d60ea254)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Investigating this section for an apparent typo it was decided
that the term needed removed. During the process I re-wrote
the section for clarity.
(From yocto-docs rev: 0ba7e364a49328a2cd57f67ed1a540bfeffc9e08)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
Some edits to remove a link to the YP Metadata definition.
The metadata referred to here is for opkg only.
(From yocto-docs rev: 777969fb3b74e638fedb638d161e2f92ac0a5f4c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
Added a cross-reference link for this variable into the glossary.
(From yocto-docs rev: a6f4935b60222a97a5fe03a538a3f8042e18d3f6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
As part of the fix for this bug, I have added a description of this
variable to the glossary.
(From yocto-docs rev: ad988c82b364bb0c629bcb2ce04f99e0e371622e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Three chunks attempted in a patch from Robert. Two out of
three worked. One did not because the text had changed due
to re-writing a note that had some links to out-of-date
wiki pages.
(From yocto-docs rev: 7f807d6df4842d47534c4011ccf67fd01bf0b830)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch from Robert P. J. Day. Good catches for some minor
wordings and such.
(From yocto-docs rev: 44c98e879bddfee49a5b89e7bb9c94c403284140)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch applied from Robert P. J. Day that basically amounted to
a good review of this section. Robert caught several typos and
small writing issues throughout the section.
(From yocto-docs rev: e44bb5897dbcc7e96bfbc730f6abe87cc2df2f3f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5408]
The developer's manual should only refer to functionality which
is available in oe-core. Currently, this passage requires the
user to add a package from, and use facilities of, meta-oe. This
fix describes how to use facilities in oe-core to the same end.
(From yocto-docs rev: 2dfaa88ae4760f86dbbdc8b58de7feba25a8014a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two links in the section discussing Linux distro requirements to
wiki pages were terribly out of date. I have rewritten the note
to remove them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 918e2e9d1146e828a2bbd16d8f5bad837effe088)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The links to the supplemental information wiki pages on setting up
your system to run YP were terribly out of date. I re-wrote the
section to remove them.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0a2a2b95781e6b70d584612c33f81839cf7a10c1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The formatting for the "Caution" boxes was poor. There was no
apparent reason in the style guide why these types of admonitions
should appear any different than "Notes" or "Tips", which look
fine. I could not devise a .css solution so I tricked the
formatting by using the <title></title> tags in combination with
a <note></note> pair. Basically dumped the <caution></caution>
tag pair. It looks okay now.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: a53d6f0b3a22cfd87f841c03452b5ebce2b1b474)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5440]
Needed to add this to Ubuntu and Debian as an essential package.
Updated the variable so that both the QS and ref-manual will
have the package listed.
(From yocto-docs rev: 3b5b198c971af12cfe395c3828e01f7fb369e7a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The etcdir string was replaced by sysconfdir.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 095a9226171189f17c0671b05196cef58da33732)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable is only used when building an image using Hob.
The description implied otherwise. I clearly state this now.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 12b671aec1df367c107d906bbefb44da56b2adec)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Looking at the code, it should be ICECC_USER_PACKAGE_BL and not
ICECC_PACKAGE_BL here, and also fix "localy" -> "locally".
Thanks to Scott Rifenbark for pointing this out.
(From OE-Core rev: b325e46059efe6974abf01131dca3f2094a6bf90)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
image.bbclass now depends on virtual/kernel:do_deploy, so add a task for that.
This fixes errors like this:
ERROR: Task do_build in /build/linaro/build/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-lng.bb depends upon non-existent task do_deploy in /build/linaro/build/openembedded-core/meta/recipes-kernel/linux/linux-dummy.bb
(From OE-Core rev: 26d07f2a5bef42a113c9c81f2b5701b4f3d10d47)
Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I've always found it somewhat annoying that this icon's rotation
animation wasn't quite correct; this was because it was looping around
to the second position instead of the first, which made it appear to
stutter.
(Bitbake rev: 78ad15b669b9c7cde41f7bd1ab884c1d2e0db91b)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you had more than 15 layers the system would crash since one more
value is added to one array than the other. This fixes the code
so equal numbers of values are added to the arrays and hence
doesn't crash when many layers are enabled.
(Bitbake rev: 4e65463886a2ef245b2f8974e82e9cb942af224b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The idea is to build on the --status-only option for bitbake and
expose a mechanism where the oe init scripts can easily switch between
memres server and the non-memres server.
In the case of the standard oe init script the following
can shut down the server:
if [ -z "$BBSERVER" ] && [ -f bitbake.lock ] ; then
grep ":" bitbake.lock > /dev/null && BBSERVER=`cat bitbake.lock` bitbake --status-only
if [ $? = 0 ] ; then
echo "Shutting down bitbake memory resident server with bitbake -m"
BBSERVER=`cat bitbake.lock` bitbake -m
fi
fi
A similar function can be used to automatically detect if the server
is already running for the oe memres init script. This new
functionality allows for the memres init script to be started in a new
shell and connect up to an alaready running server without seeing the
error of trying to start the server multiple times.
(Bitbake rev: b1803958de8d7c3c3279841e38604a08dc2316cc)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch adds the ability to dynamically select a port for the
bitbake memory resident server when the BBSERVER port is set to -1.
This allows for running multiple instances of the bitbake memory
resident server on the same system in different build directories.
The client portion of the bitbake instance can also request that the
server automatically start when using the auto port feature. This is
to deal with a bitbake instance that eventually times out and exits or
that has died for some unknown reason.
The new functionality allows for lazy startup of the server after
sourcing the init script for the memory resident functionality.
(Bitbake rev: d6abc07ff385357d312d8435b89e0a9c1f965433)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The --status-only option is purely to check the health of the server.
The idea is to use it from the oe environment script so as to know if
the server needs to be started or not.
(Bitbake rev: 46b26ef5c27bfa9c91680f494f02750305b8098c)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to run multiple bitbake memory resident servers on the same
machine they must each use different ports.
This patch works in conjuction with bitbake to make the auto port
selection and lazy server startup the default.
(From OE-Core rev: 9cf1ac73c4e35101a4f5c01a5e1c53f9d567bc58)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use the bitbake --status-only and the fact that bitbake.lock will
contain the host name and port to determine when to activate or
shutdown the stay resident bitbake server.
This allows a end developer to cleanly switch between the two ways to
use bitbake as well as enter the memres bitbake server from multiple
shells without starting the server if it is already running.
(From OE-Core rev: d71059c86a8160f39af6ddfdd30c86835f4eb959)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When fortran was enabled, builds were failing due to a extra files.
For now we can remove these and avoid the build failure.
(From OE-Core rev: 2e60ef7fe63974e443a9ddc25c5eb4249ec37963)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is little point in including the file twice so lets not. The
main recipe already included it.
(From OE-Core rev: b3cccee0c66ce744a79843a5dd9798475c84e23c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently bitbake only adds files to its dependency list if they exist.
If you add 'include foo.inc' to your recipe and the file doesn't exist,
then later you add the file, the cache will not be invalidated.
This leads to another bug which is that if files don't exist and then
you add them and they should be found first due to BBPATH, again the
cache won't invalidate.
This patch adds in tracking of files we check for the existence of so
that if they are added later, the cache correctly invalidates. This
necessitated a new version of bb.utils.which which returns a list of
files tested for.
The patch also adds in checks for duplicate file includes and for now
prints a warning about this. That will likely become a fatal error at
some point since its never usually desired to include a file twice.
The same issue is also fixed for class inheritance. Now when a class
is added which would be found in the usual search path, it will cause
the cache to be invalidated.
Unfortunately this is old code in bitbake and the patch isn't the
neatest since we have to work within that framework.
[YOCTO #5611]
[YOCTO #4425]
(Bitbake rev: 78d285871e4b8c54ccc4602d571e85f922e37ccd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ICU presence is auto-detected at configure time and until recently (e68850 and
d61230) was pulled into most builds through harfbuzz and beecrypt. Now it's
floating and this leads to build failures.
As in all likelihood the majority of people were building this with ICU enabled,
add an explicit dependency.
(From OE-Core rev: 46dcec6fd455584d9b5d0d7ff1e5b36fbe5a2d62)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
WARNING: QA Issue: sqlite3: configure was passed unrecognised options: --disable-tcl
There is no tcl option or support now so remove the option.
(From OE-Core rev: 7d1fd11e50a280bcc3e6c2160871cdef14864cc2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.10 SRCREVs for the following fixes:
f47ea28 bridge: enable EBTABLES
a9ec82e e1000: prevent oops when adapter is being closed and reset simultaneously
a4e1bd7 Revert "arm: add dummy swizzle for versatile with qemu"
(From OE-Core rev: 20139a693677c23324c89c963735f3b8c18eeb84)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the 3.4 kernel to the latest korg -stable release.
(From OE-Core rev: b9049f6394d58610ecd3b0c77ccee5ef95ebdb73)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto-3.10 SRCREVs to the latest korg -stable
release.
(From OE-Core rev: 1da738722c9f81260dfbada6a97a21eb812d20a1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To mips64 libn32, The HOST_SYS is mips64-*-linux-gnun32, the COMPATIBLE_HOST
is mips64.*-linux, the regular expression matching both will return true. so
append the ending position word into COMPATIBLE_HOST to make match failure
(From OE-Core rev: f5c4d18c1b0d8a252abb3b1f67f05a1689b3ea67)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: c8d687f409a19312b34e215e7caaa39199598ed0)
Signed-off-by: Li Wang <li.wang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: a3f3f44f9a064a0158ce9ad12af7a7cb26042c97)
Signed-off-by: Li Wang <li.wang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 12c4094ce118569f9518e1b0625d110251595ef0)
Signed-off-by: Li Wang <li.wang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add busybox_git.bb recipe so that it would be easier to hack with
busybox. Set DEFAULT_PREFERENCE to "-1" in the git recipe so that we
still use the busybox_1.21.1.bb recipe by default.
(From OE-Core rev: d290bbe6d9826fbcfa2e0a7624886284697ed7eb)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The carl9170fw is unbuilt, needs specialise toolchains, cmake and so on
so we might as well delete it (and lose the bash dependnecy).
Equally, the top level bash dependency from the empty configure script is
pointless.
[YOCTO #5555]
(From OE-Core rev: e2b62393497a0aaffb21161336a42249db61a10d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scott Rifenbark
Robert P. J. Day
Trevor Woerner
Cristiana Voicu
Paul Eggleton
Koen Kooi
Richard Purdie
Jason Wessel
Ross Burton
Bruce Ashfield
Roy Li
Li Wang
Chen Qi