summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2016-09-09clutter-1.0: do not use the prepackaged clutter.types file when generating ↵Alexander Kanavin2
gtk-doc Doing so will fail when x11 is disabled in particular. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09pango: fix gtk-doc build when x11 is not in useAlexander Kanavin2
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09util-linux: do not enable gtk-doc and explain whyAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09p11-kit: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libsoup-2.4: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libtasn1: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gnutls: enable gtk-docAlexander Kanavin1
gtk-doc also requires --enable-doc, so that is no longer configurable. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09harfbuzz: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09cairo: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libenck3: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libgudev: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09json-glib: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gnome-desktop3: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gdk-pixbuf: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libuser: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libidn: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09orc: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09dbus-glib: enable gtk-docAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09webkitgtk: re-enable introspection on powerpcAlexander Kanavin1
It seems to work under qemu-ppc now. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gcr, libsecret, webkitgtk: disable gtk-doc on mips64Alexander Kanavin3
It fails with the same error as gobject-introspection Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gcr: disable gtk-doc on x86_64Alexander Kanavin1
For same reason that introspection is disabled: the transient binary goes into infinite loop. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gtk+3: disable gtk-doc when x11 is not availableAlexander Kanavin1
gtk-doc requires gdk/x11/gdkx.h which is not available if gdk x11 backend is disabled (due to jku's patch). Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09webkitgtk: enable gtk-doc supportAlexander Kanavin2
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gstreamer1.0: enable gtk-doc supportAlexander Kanavin5
check support is no longer disabled by default because it is a requirement of gtk-doc support in gstreamer. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09libglade: remove the recipeAlexander Kanavin4
Libglade has been obsolete for several years and is used by nothing in oe-core; it will be moved to meta-oe so that old recipes still present there continue to build. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09systemd: drop unused gtkdoc-related variableAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09kmod: do not let gtkdocize failAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gtk-doc.bbclass: enable building gtk-doc based documentationAlexander Kanavin1
This is done similarly to gobject-introspection, but with much less delicate hacking around the upstream way of working. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09gtk-doc: add a recipe, remove gtk-doc-stubAlexander Kanavin5
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09source-highlight: add a recipeAlexander Kanavin3
gtk-doc relies on this to highlight source code snippets Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-09-09oeqa: Use snapshot instead of copying the rootfs imageRichard Purdie2
Rather than copying images, use the snapshot option to qemu. This fixes a regression caused by the recent runqemu changes where the wrong images were being testes since the image is copied without the qemuboot.conf file. This means the latest image is found by runqemu rather than the specified one, leading to various confused testing results. It could be fixed by copying more files but use snapshot mode instead. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09scripts/runqemu: Add snapshot supportRichard Purdie1
Allow access to the snapshot option of qemu to simplify some of our runtime testing to avoid copying images. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: Enable virtio RNG for all platformsRichard Purdie1
We have problems where systems simply stop booting and hang. This is due to a lack of entropy which means ssh keys and networking can't be brought up. Adding in the virtio-rng passthrough support allows host entropy to pass into the guess and avoids these hangs. This is particularly problematic after the gnutls upgrade which starts using /dev/random instead of /dev/urandom but was an issue we'd occasionally seem before that. It particualrly affected x86 and ppc machines for some reason. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: Update to modern prefrerred net syntaxRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: Allow unique network interface MAC addressesRichard Purdie3
Current qemu instances all share the same MAC address. This shouldn't be an issue as they are all on separate network interfaces, however on the slight chance this is causing problems, its easy enough to ensure we use unique MAC addresses based on the IP numbers we assign. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemurunner.py/qemutinyrunner.py: remove runqemu-internalRobert Yang2
There is no runqemu-internal any more. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09nativesdk-qemu-helper: fix for new runqemuRobert Yang1
There is no runqemu-internal anymore, and it is a python script now which requires several python modules. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: fix run from testimage with non-standard DEPLOY_DIR_IMAGEJoshua Lock1
testimage.bbclass uses runqemu to execute runtime tests on a qemu target, this means that bitbake is already running and `bitbake -e` can't be called to obtain bitbake variables. runqemu tries to work around being unable to read values for bitbake variables by inferring the MACHINE from the DEPLOY_DIR_IMAGE setting, however if a user sets that variable in a manner which doesn't follow the systems expectations (i.e. if running `bitbake -c testimage` against a directory of pre-generated images in a user-specified path) the inferring of the MACHINE name from the DEPLOY_DIR_IMAGE location will fail. It's possible that check_arg_machine() shouldn't cause runqemu to fail and that runqemu should proceed with the user-supplied value even if it can't be verified. This patch simply ensures that a workflow where the user sets DEPLOY_DIR_IMAGE continues to work without changing too much of the runqemu code. [YOCTO #10238] Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: fixes for when invoked during a bitbake runJoshua Lock1
When runqemu is invoked from a running bitbake instance it will be unable to call `bitbake -e` due to the lock held by the calling bitbake instance. Our test code sets an OE_TMPDIR environment variable from which we can infer/guess paths. Add code to do so when self.bitbake_e can't be set, much as the sh version of runqemu did. [YOCTO #10240] Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: better handle running on a host with different pathsJoshua Lock1
If the STAGING_*_NATIVE directories from the config file don't exist and we're in a sourced OE build directory try to extract the paths from `bitbake -e` Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: assume artefacts are relative to *.qemuboot.confJoshua Lock1
When runqemu is started with a *.qemuboot.conf arg assume that image artefacts are relative to that file, rather than in whatever directory the DEPLOY_DIR_IMAGE variable in the conf file points to. Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09runqemu: refactor it and remove machine knowledgeRobert Yang2
Previously, runqemu had hard coded machine knowledge, which limited its usage, for example, qemu can boot genericx86, but runqemu can't, we need edit runqemu/runqemu-internal a lot if we want to boot genericx86. Now bsp conf files can set vars to make it can be boot by runqemu, and qemuboot.bbclass will save these info to DEPLOY_DIR_IMAGE/qemuboot.conf. Please see qemuboot.bbclass' comments on how to set the vars. * Re-write it in python3, which can reduce lines from 1239 to about 750 lines * All the machine knowledges are gone * All of the TUN_ARCH knowledge are gone * All the previous options are preserved, and there is a new way to run runqemu: (it doesn't need run "bitake -e" in such a case) $ runqemu tmp/deploy/images/qemux86 or: $ runqemu tmp/deploy/images/qemuarm/<image>.ext4 or: $ runqemu tmp/deploy/images/qemuarm/qemuboot.conf * Fixed audio support, not limited on x86 or x86_64 * Fix SLIRP mode, add help message, avoid mixing with tap * Fix NFS boot, it will extract <image>.tar.bz2 or tar.gz to DEPLOY_DIR_IMAGE/<image>-nfsroot when no NFS_DIR, and remove it after stop. * More bsps can be boot, such as genericx86 and genericx86-64. * The patch for qemuzynq, qemuzynqmp, qemumicroblaze has been sent to meta-xilinx' mailing list. * I can't find any qemush4 bsp or how to build it, so it is not considered atm. [YOCTO #1018] [YOCTO #4827] [YOCTO #7459] [YOCTO #7887] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemu.inc: inherit qemuboot.bbclassRobert Yang1
All qemu boards should be able to boot by runqemu. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemuppc: Use virtio networking instead of pcnetRichard Purdie1
qemuppc can use virtio networking and we may as well do so for better prformance as we do under the other emulated hardware. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemuppc.conf: set vars for runqemuRobert Yang1
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemumips/qemumips64.conf: set vars for runqemuRobert Yang3
Add qemuboot-mips.inc to reduce duplicated code, the various mips bsps which can be boot by runqemu can require qemuboot-mips.inc Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemux86.conf/qemux86-64.conf: set vars for runqemuRobert Yang3
Add qemuboot-x86.inc to reduce duplicated code, the x86/x86_64 bsps which can be boot by runqemu can require qemuboot-x86.inc. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemuarm64.conf: set vars for runqemuRobert Yang1
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemuarm.conf: set PREFERRED_VERSION_linux-yoctoRobert Yang1
The base_version_less_or_equal() will raise errors if PREFERRED_VERSION_linux-yocto is None. For example, when we build DISTRO = "nodistro", PREFERRED_VERSION_linux-yocto is not be defined since it is defined in poky.conf, and then bitbake will choose the higher version which is 4.8 currently, so set PREFERRED_VERSION_linux-yocto to 4.8, otherwise, runqemu can't boot it. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemuarm: Add DTB file new kernelRichard Purdie1
For kernels after 4.7, we need to ensure the DTB file for the kernel is used by runqemu. Doing this conditionally based upon the kernel verison being built seems to be the only way forward for this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-13 14:31:17 +0000