Since the extrausers class is only useful for image recipes, it is
better to suggest adding it via IMAGE_CLASSES instead of INHERIT in the
example.
Also make the example a bit more readable by indenting the variable
values.
(From meta-yocto rev: 7905aa1ff174e66c5c520b2a4fcc1f0d3863baad)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adds documentation to explain that src-pkgs can be added to
EXTRA_IMAGE_FEATURES
(From meta-yocto rev: 9b00dcb40b7b8a1aeb57fa8447900cf1fe832e2e)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While not strictly required, list shadow-base as the example to use for
VIRTUAL-RUNTIME_login_manager when configuring for systemd. This
provider matches what is found in for example Debian and is also one of
the non-intuitive VIRTUAL-RUNTIME alternatives, so it's good to have an
example in use somewhere.
(From meta-yocto rev: 7a75d20f1361a64bebfd2ad228ebde1a823fd239)
Signed-off-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is now in default-distrovars, so remove it from poky.conf.
(From meta-yocto rev: 4da8ef338252667696b82141ae67d0b426255fbe)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
mirrors.bbclass already adds downloads.yoctoproject.org/mirror/sources for FTP
and HTTP to ${MIRRORS} so there's no need to do it again.
(From meta-yocto rev: 67b79df4fbffcf677f8d127c00672f0d7c6c434b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This overrides the default assignment in qemu.inc and in doing so removes
RISC-V.
(From meta-yocto rev: 8cc9423649b2702c0ded721244a017b371b3a244)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is now in the default HOSTTOOLS so can be removed from here.
(From meta-yocto rev: 74bd707f129975a74c3b99a6744681da96f39f75)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These tests are very old, unmaintained, and there are better benchmarking
systems available now.
(From meta-yocto rev: 48b446fe7ee6601e8927a2f6663c98e6c42e9064)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If DISTRO_VERSION is defined using an override, e.g., by defining it
in auto.conf as DISTRO_VERSION_forcevariable, then the unoverridden
value was still used in SDK_VERSION since it was defined using the :=
operator. However, there should be no reason to define SDK_VERSION
this way.
Also use getVar to access the variable to ensure tracebacks from problems
are less confusing.
[RP: Tweaked commit message]
(From meta-yocto rev: 74f43fb82a93eecfe7519a87fdf1cb0152d56b48)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replace SDK_ARCH with SDKMACHINE so that SDK targeting different
development machines but having the same architecture don't cause
similar errors as found in '3614dd4aee9 ("poky.conf: Add MACHINE to
SDK_NAME")'
This doesn't have any effect on the SDK machines provided in oe-core,
since SDK_ARCH is the same as SDKMACHINE for all of them.
(From meta-yocto rev: 951184fd62b3ab14266f300defd47d3c5c09ad9b)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid errors from:
MACHINE=qemux86-64 bitbake core-image-sato:do_populate_sdk
then:
MACHINE=genericx86-64 bitbake core-image-sato:do_populate_sdk
which gives:
ERROR: core-image-sato-1.0-r0 do_populate_sdk: The recipe core-image-sato is trying
to install files into a shared area when those files already exist. Those files and
their manifest location are:
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.host.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.testdata.json
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.target.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.sh
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
Please verify which recipe should provide the above files.
Adding MACHINE to the artefact name will avoid this. The issue was highlighted by
changes to the autobuilder configuration.
(From meta-yocto rev: 3614dd4aee9d19f1024edb6a36b2862c2d726c04)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, this is a QA warning by default, howver its a useful
check to catch configuration errors, where we might have forgotten
to update or adapt configure options on updates/upgrades to a package
(From meta-yocto rev: a75ad2e4227f715146fc1e07f9abef4e80c1aa12)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4.18 will be the newest kernel in the upcoming release, so we bump
our default to it in preparation of 4.15 being dropped.
(From meta-yocto rev: 698c1edd9a258a891b7f1373c3468218e6440856)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This has been an opt-in for so long, some distributions e.g.
poky-lsb uses it by default however, since most of linux
distros have started to default to these settings for security
enhancements, time has come for OE to make it default too
(From meta-yocto rev: 81bf1019c8601da952242fbcc827e0bef1ff25d7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is in default distro config now
(From meta-yocto rev: c85fa6a397d7ed97779ce347d4013cd1ea99d53f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Qemu now builds with libsdl2, so update the local.conf.sample to reflect this.
(From meta-yocto rev: 5e187b5b3dc69f0e8e5a2956e7fe997e62cb48c9)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the default kernel for qemu* to be v4.15. This allows easy
integration of the latest fixes/features for new BSPs. 4.14 is also
available as a LTS kernel option.
(From meta-yocto rev: cdd79c0f879e5e4c480773c4507f921533e17914)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4.14 is a LTS/LTSI kernel and we are dropping anything older than
4.12 in master. As such, we make 4.14 the default for poky-lsb.
(From meta-yocto rev: ba6d172fd405dcc28c13f73aec1d1034a10bfc1d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For various reasons we need to be able to set and override this from
auto.conf on our test infrastructure. We have tried forcing the variable
but this then breaks other selftests. In the interests of not complicating
things further and needing to modify the tests across releases, weaken
the default assignment.
(From meta-yocto rev: be0a707eea3f0015eb7e2df2d1fd07164c2a627d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The beaglebone BSP provided in this layer is a reference implementation
usingonly mainline components available in core Yocto Project layers,
whereas Texas Instruments maintain a full-featured BSP in the meta-ti
layer.
Rename the reference machine to prevent namespace collisions with the
version maintained by the SoC vendor.
[YOCTO #12326]
(From meta-yocto rev: e32882938eca7f50548deab84dab78b4aef31b95)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fedora 24 reached end-of-life on 2017-08-08 and hasn't been tested in
some time.
* Fedora 25 reaches end-of-life in Q4 2017 and is exhibiting a bug which
makes it an extremely unreliable host OS for workers on the Yocto
Autobuilder. For that reason we'll no longer be using this distro on the
Yocto Autobuilder and thus cannot claim the distro is sanity tested.
(From meta-yocto rev: 976ee9a60ab786ae07057577975e3b91e388cd47)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have been working with OE on debian-9 for several months now without
issue. In addition, I tested a build + runqemu for core-image-sato
following the quickstart guide and had no issues.
(From meta-yocto rev: 2d8a572df7498ce8eb3a78f05384f0f7dd5ecb91)
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The YP Compat v2 standard requres a more specific README structure. Bring
meta-yocto to the required standard and clean up some of the data in the
READMEs whilst in there.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This should have been done after Pyro was released, but it apparently
slipped though the cracks.
(From meta-yocto rev: 4e6dc6596fd60c35e14ad95899ebd66d16375d77)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The header text has been moved to meta/conf/conf-notes.txt by:
[ meta: move some text from oe-setup-builddir to conf-notes.txt ]
Need do the same to meta-poky/conf/conf-notes.txt.
(From meta-yocto rev: 8a9d72abcf484fbe8001a08623910c5af1be07a0)
Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Due to the age of 4.1 and it being removed from oe-core master
as an active kernel, we can bump poky-lsb to the newer 4.9 LTSI
kernel version.
(From meta-yocto rev: 1f85cc33429e9a217a11adc298e2149f2950724c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
