MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 21:09:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
47,489 Commits 39 Branches 594 Tags 250 MiB
Python 53.7%
BitBake 12.7%
HTML 10.9%
Roff 6.2%
Pawn 3.6%
Other 12.3%
3fde63363a
Go to file
Paul Eggleton 3fde63363a devtool: ensure recipes devtool is working on are unlocked within the eSDK 
Alongside reworking the way devtool extracts source, we now need to
ensure that within the extensible SDK where task signatures are locked,
the signatures of the tasks for the recipes being worked on get unlocked
at the right time or otherwise we'll now get taskhash mismatches when
running devtool modify on a recipe that was included in the eSDK such as
the kernel (due to a separate bug). The existing mechanism for
auto-unlocking recipes was a little weak and was happening too late, so
I've reimplemented it so that:
(a) it gets triggered immediately when the recipe/append is created
(b) we avoid writing to the unlocked signatures file unnecessarily
    (since it's a global configuration file) and
(c) within the eSDK configuration we whitelist SIGGEN_UNLOCKED_RECIPES
    to avoid unnecessary reparses every time we perform one of the
    devtool operations that does need to change this list.

Fixes [YOCTO #11883] (not the underlying cause, but this manifestation
of the issue).

(From OE-Core rev: 4e9a0be32fc30fb87d65da7cd1a4015c99533aff)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-18 11:07:29 +01:00
bitbake bitbake: toaster: allow dots in user path names 2017-09-17 23:24:14 +01:00
documentation kernel-dev: Updates to the kernel flow procedures 2017-09-13 18:00:19 +01:00
meta devtool: ensure recipes devtool is working on are unlocked within the eSDK 2017-09-18 11:07:29 +01:00
meta-poky meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
meta-selftest oeqa: increase verbosity of dnf commands in dnf packagefeed test 2017-08-18 23:46:38 +01:00
meta-skeleton meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf 2017-06-12 15:08:30 +01:00
meta-yocto-bsp meta-yocto-bsp: bump to the latest linux stable kernel for the non-x86 BSPs 2017-09-17 23:23:21 +01:00
scripts devtool: ensure recipes devtool is working on are unlocked within the eSDK 2017-09-18 11:07:29 +01:00
.gitignore add !meta-poky to .gitignore file 2016-03-26 08:06:58 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
oe-init-build-env oe-init-build-env-memres: Drop it 2017-07-21 08:44:25 +01:00
README.hardware meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.LSB README.LSB: describe oe-core's deviations from the LSB spec 2017-06-28 15:52:17 +01:00
README.poky meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.qemu README.qemu: Add from meta-yocto as it belongs in core 2017-09-14 13:36:00 +01:00

README.qemu 

QEMU Emulation Targets
======================

To simplify development, the build system supports building images to
work with the QEMU emulator in system emulation mode. Several architectures
are currently supported in 32 and 64 bit variants:

  * ARM (qemuarm + qemuarm64)
  * x86 (qemux86 + qemux86-64)
  * PowerPC (qemuppc + qemuppc64)
  * MIPS (qemumips + qemumips64)

Use of the QEMU images is covered in the Yocto Project Reference Manual.
The appropriate MACHINE variable value corresponding to the target is given
in brackets.