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
54,830 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%
b52d58b8bb
Go to file
Paul Eggleton b52d58b8bb devtool: upgrade: fix handling of errors parsing upgraded recipe 
As part of upgrading a recipe we create the upgraded recipe file in the
workspace and then try to parse it so we can then make further
modifications. If for some reason that parsing fails then the failure
was not being handled very well - the broken recipe was being left in
place, breaking parsing until it was removed by hand. Fix that by adding
a call to the cleanup function, and fix the following issues:

* Fix the cleanup function which doesn't look like it has ever worked
  due to a typo in the function call

* Fix double-printing the error message

* Remove usage of DevtoolError in this case (DevtoolError is for simple
  usage errors, not this kind of issue which may be the result of a
  bug).

We're still printing a traceback in this scenario but at least it
doesn't break the build system requiring manual cleanup. I also
introduced a command-line option to preserve the broken upgraded recipe
file(s) for debugging purposes.

(The reproducer for this is "devtool upgrade libnewt-python", however
you need to check out revision b82ea144e1
or earlier since that recipe has now been absorbed into the libnewt
recipe. The libnewt-python recipe was causing an issue with the upgrade
because it actually included the libnewt recipe using ${PV} in the
include statement, and of course PV was changing in the upgrade.)

Fixes [YOCTO #13404].

(From OE-Core rev: c519ac360796675d7fc09a5250d21f0f5b6236fc)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-07-03 17:00:57 +01:00
bitbake bitbake: bitbake: toaster:tests: python -> python3 2019-06-28 13:29:04 +01:00
documentation dev-manual: Fixed grammar issue. 2019-06-18 11:29:23 +01:00
meta libcap-ng: do not use symlink to share files with libcap-ng-python 2019-07-03 17:00:57 +01:00
meta-poky local.conf.sample.extended: remove redundant RUNTIMETARGET assignment 2019-06-24 17:34:25 +01:00
meta-selftest fortran-helloworld: add a very dumb Fortran Hello World for testing 2019-06-27 12:20:36 +01:00
meta-skeleton meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
meta-yocto-bsp beaglebone-yocto: Add missing wic image u-boot deploy dependency 2019-06-01 11:27:42 +01:00
scripts devtool: upgrade: fix handling of errors parsing upgraded recipe 2019-07-03 17:00:57 +01:00
.gitignore gitignore: Ignore repo tool directory 2018-10-29 17:26:47 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
LICENSE.GPL-2.0-only meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
LICENSE.MIT meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
oe-init-build-env meta/lib+scripts: Convert to SPDX license headers 2019-05-09 16:31:55 +01:00
README.hardware meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.LSB pax: remove the recipe 2018-02-24 10:31:45 +00:00
README.OE-Core README: Rename to README.OE-Core so its clear where its from/belongs/is about 2019-03-06 23:09:10 +00:00
README.poky meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.qemu README.qemu: qemuppc64 is not supported 2017-10-16 23:54:31 +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 only)
  * 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.