summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* lib/oe/copy_buildsystem: fix building eSDK with indirect paths in BBLAYERSpaule/extsdk-path-fixesPaul Eggleton2016-09-141-2/+2
| | | | | | | | | | | | | | | Indirect paths (e.g. ${TOPDIR}/../meta-something) do generally work if used in BBLAYERS in bblayers.conf. However, if you built an extensible SDK with this configuration then the creation of the workspace within the SDK using devtool in do_populate_sdk_ext failed. This is because the copy_buildsystem code was no longer correctly recognising that the core layer ("meta") was part of a repository (e.g. openembedded-core / poky) that should be shipped together - because of the indirection - and thus it was splitting out the meta directory, and a number of places in the code assume that the meta directory is next to the scripts directory. Use os.path.abspath() to flatten out any indirections. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* classes/populate_sdk_ext: ensure we clean the right temporary TMPDIR pathPaul Eggleton2016-09-141-3/+4
| | | | | | | | | | | | | | | | | | After we run the build system within the eSDK internally as part of the sstate filtering that happens during do_populate_sdk_ext, we need to ensure that the TMPDIR created during that process gets deleted. However we were using the TMPDIR path for the build producing the eSDK which may not be the same (since that value would typically be filtered out) thus if the user had set TMPDIR to something other than the default, the temporary TMPDIR would not be deleted which not only led to extraneous junk entering the SDK but also failures during install because the TMPDIR path was different. In order to fix this, force TMPDIR to a known value during the sstate filtering run so we know what to delete afterwards. Fixes [YOCTO #10210]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
* oeqa.runtime.smart: work around smart race issuesMarkus Lehtonen2016-09-091-0/+25
| | | | | | | | | | | | | Yucku hack around test failures which ultimately are caused by a race in smartpm itself. Issuing smartpm commands in quick succession causes races in package cache of smartpm on some systems. This patch mitigates the problem by sleeping for 1 second after each smartpm command that modifies the system. [YOCTO #10244] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/smart: Prune feeds to save memoryRichard Purdie2016-09-091-0/+4
| | | | | | | | | | Full package feed indexes overload a 256MB image so reduce the number of rpms the feed. Filter to p* since we use the psplash packages and this leaves some allarch and machine arch packages too. [YOCTO #8771] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: only depend on native gtk-doc for documentation generationRoss Burton2016-09-091-1/+1
| | | | | | | | Now that gtk-doc-native works correctly, the gtk-doc class doesn't need to depend on target gtk-doc. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: use pkg-config-native in native gtk-doc.m4Ross Burton2016-09-092-1/+35
| | | | | | | | | | | | When building gtk-doc-native the m4 functions for autoconf should use pkg-config-native instead of pkg-config so that they can find the native tooling. This means that it is possible to generate gtk-doc without building the target packages. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer: remove packaged copy of gtk-doc.m4Ross Burton2016-09-092-0/+2
| | | | | | | The gstreamer common module ships a copy of gtk-doc.m4 that will be used in preference to our patched form, so delete it before configure is executed. Signed-off-by: Ross Burton <ross.burton@intel.com>
* gobject-introspection: set GI_SCANNER_DISABLE_CACHE for nativeRobert Yang2016-09-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The native recipe should not write files to $HOME/.cache as target, this can avoid problems when multi builds are running on the same host like: | File "./g-ir-scanner", line 66, in <module> | sys.exit(scanner_main(sys.argv)) | File "../gobject-introspection-1.48.0/giscanner/scannermain.py", line 543, in scanner_main | transformer = create_transformer(namespace, options) | File "../gobject-introspection-1.48.0/giscanner/scannermain.py", line 389, in create_transformer | symbol_filter_cmd=options.symbol_filter_cmd) | File "../gobject-introspection-1.48.0/giscanner/transformer.py", line 54, in __init__ | self._cachestore = CacheStore() | File "../gobject-introspection-1.48.0/giscanner/cachestore.py", line 61, in __init__ | self._check_cache_version() | File "../gobject-introspection-1.48.0/giscanner/cachestore.py", line 89, in _check_cache_version | self._clean() | File "../gobject-introspection-1.48.0/giscanner/cachestore.py", line 141, in _clean | self._remove_filename(os.path.join(self._directory, filename)) | File "../gobject-introspection-1.48.0/giscanner/cachestore.py", line 123, in _remove_filename | os.unlink(filename) | FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/.cache/g-ir-scanner/0a47aa95823c95a0b5d1bd610b60d02f35785f26' | Makefile:3518: recipe for target 'GModule-2.0.gir' failed Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro-alias.inc: rename gtk-doc-stub to gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* clutter-1.0: do not use the prepackaged clutter.types file when generating ↵Alexander Kanavin2016-09-092-0/+144
| | | | | | | | gtk-doc Doing so will fail when x11 is disabled in particular. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* pango: fix gtk-doc build when x11 is not in useAlexander Kanavin2016-09-092-0/+148
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* util-linux: do not enable gtk-doc and explain whyAlexander Kanavin2016-09-091-0/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* p11-kit: enable gtk-docAlexander Kanavin2016-09-091-1/+21
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libsoup-2.4: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libtasn1: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gnutls: enable gtk-docAlexander Kanavin2016-09-091-2/+2
| | | | | | gtk-doc also requires --enable-doc, so that is no longer configurable. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* harfbuzz: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* cairo: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libenck3: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libgudev: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* json-glib: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gnome-desktop3: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gdk-pixbuf: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libuser: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* libidn: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* orc: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* dbus-glib: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* webkitgtk: re-enable introspection on powerpcAlexander Kanavin2016-09-091-6/+0
| | | | | | It seems to work under qemu-ppc now. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gcr, libsecret, webkitgtk: disable gtk-doc on mips64Alexander Kanavin2016-09-093-3/+3
| | | | | | It fails with the same error as gobject-introspection Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gcr: disable gtk-doc on x86_64Alexander Kanavin2016-09-091-1/+1
| | | | | | For same reason that introspection is disabled: the transient binary goes into infinite loop. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gtk+3: disable gtk-doc when x11 is not availableAlexander Kanavin2016-09-091-0/+1
| | | | | | | 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>
* webkitgtk: enable gtk-doc supportAlexander Kanavin2016-09-092-2/+52
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gstreamer1.0: enable gtk-doc supportAlexander Kanavin2016-09-095-10/+42
| | | | | | | 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>
* libglade: remove the recipeAlexander Kanavin2016-09-094-648/+0
| | | | | | | 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>
* systemd: drop unused gtkdoc-related variableAlexander Kanavin2016-09-091-2/+0
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* kmod: do not let gtkdocize failAlexander Kanavin2016-09-091-1/+1
| | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* gtk-doc.bbclass: enable building gtk-doc based documentationAlexander Kanavin2016-09-091-14/+58
| | | | | | | 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>
* gtk-doc: add a recipe, remove gtk-doc-stubAlexander Kanavin2016-09-095-338/+218
| | | | | Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* source-highlight: add a recipeAlexander Kanavin2016-09-093-0/+59
| | | | | | gtk-doc relies on this to highlight source code snippets Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
* oeqa: Use snapshot instead of copying the rootfs imageRichard Purdie2016-09-092-8/+3
| | | | | | | | | | | | 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>
* scripts/runqemu: Add snapshot supportRichard Purdie2016-09-091-0/+6
| | | | | | | 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>
* runqemu: Enable virtio RNG for all platformsRichard Purdie2016-09-091-0/+3
| | | | | | | | | | | | | | | 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>
* runqemu: Update to modern prefrerred net syntaxRichard Purdie2016-09-091-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Allow unique network interface MAC addressesRichard Purdie2016-09-093-4/+5
| | | | | | | | | 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>
* qemurunner.py/qemutinyrunner.py: remove runqemu-internalRobert Yang2016-09-092-2/+2
| | | | | | | 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>
* nativesdk-qemu-helper: fix for new runqemuRobert Yang2016-09-091-4/+5
| | | | | | | | 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>
* runqemu: fix run from testimage with non-standard DEPLOY_DIR_IMAGEJoshua Lock2016-09-091-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | 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>
* runqemu: fixes for when invoked during a bitbake runJoshua Lock2016-09-091-6/+22
| | | | | | | | | | | | | | | 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>
* runqemu: better handle running on a host with different pathsJoshua Lock2016-09-091-0/+39
| | | | | | | | | 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>
* runqemu: assume artefacts are relative to *.qemuboot.confJoshua Lock2016-09-091-1/+14
| | | | | | | | | 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>