linux/meta-openembedded.git/meta-oe/classes, branch morty

gitver: skip packages instead of panic()ing if ${GITVER} fails to expand

2017-06-26T18:35:51+00:00

`inherit externalsrc gitver` is a very useful combo to get development trees in your workspace having a ${PN}_git.bb with PV=${GITVER} coexisting with a regular ${PN}_${PV}.bb but not everyone wants to checkout all developments sources and managinging different layers for each options is quite troublesome. making `gitver` skip the .bb instead of panic()ing every time EXTERNALSRC is missing allows people to have a single development layer where packages get enabled if the right sources are present or falling back to the last release if not Signed-off-by: Alejandro Mery Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

gitver: fix broken ${GITSHA} and recursion in S when PV="${GITVER}"

2017-06-26T18:35:51+00:00

v2: * use git rev-parse instead of rev-list for consistency with get_git_pv * fix getVar() to pass `expand` as required by morty's bitbake Signed-off-by: Alejandro Mery Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

gitver: extend class to use EXTERNALSRC if set

2017-06-26T18:35:51+00:00

Signed-off-by: Alejandro Mery Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

gitver: fix try/except syntax for python3 support

2017-06-26T18:35:43+00:00

https://www.python.org/dev/peps/pep-3110/ It's backward compatible with 2.6+ Signed-off-by: Alejandro Mery Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

gitpkgv: Fix $GITPKV for a single named git source

2016-09-05T11:30:50+00:00

Recipes that fetch from a single git source, assign a name to this source and do not set SRCREV_FORMAT to this name will always get a GITPKGV value of "default", which causes version-going-backwards QA errors. Fix this by automatically determining a suitable SRCREV_FORMAT from the SRC_URI if none is set explicitly. This code does not run for multiple git sources, because bitbake's fetcher enforces setting SRCREV_FORMAT when multiple version-controlled sources are used. Signed-off-by: Clemens Lang Signed-off-by: Martin Jansa

gitkpkgv: Ensure files are closed

2016-06-08T12:55:26+00:00

This avoids warnings with python 3. Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa

autotools-bootstrap: make bootstrap package specific.

2016-05-12T15:53:30+00:00

The theory behind this bbclass was reasonable, with the primary goal being to avoid multiple downloads of gnulib, but it neglected the fact that packages would be shipping a specific version of the ./bootstrap which will support some flags but maybe not all the latest ones from the latest gnulib/build-aux/bootstrap file. I attempted to simply update the two pkgs to use the latest copy of bootstrap from gnulib but this of course triggers the descent into autoconf hell that we all know and love. Rather than futzing with the packages configure.ac and deviating from what the pkg maintainers intended and tested, we can just let the packages have independent calls to ./bootstrap with whatever flags are needed. The goal of this commit is to move the prepend out to the packages and then delete the class without any real functional change ; i.e. a purely mechanical change. Then we can adjust each package to ensure it will still build with a modern host, in an independent fashion, while keeping the main advantage of not fetching gnulib two extra times for netcf and fontforge. Signed-off-by: Paul Gortmaker Signed-off-by: Martin Jansa Signed-off-by: Joe MacDonald

waf-samba.bbclass: move to meta-networking

2016-04-01T16:05:27+00:00

The recipes that are using waf-samba were all moved to meta-networking, so move the bbclass and related cross-answers files as well. Signed-off-by: Jackie Huang Signed-off-by: Martin Jansa Signed-off-by: Joe MacDonald

waf-samba.bbclass: add cross-answers option and files

2016-03-02T19:47:23+00:00

--cross-execute uses qemu to run cross-compiled binaries, it works fine for qemu supported targets, but it definitely will fail if the target is not supported by qemu. So we need to use the cross-answers option. Added three methods and set 'answer' as default: 1. answers: Only --cross-answers - try the cross-answers file, and if there's no corresponding answer, add to the file and mark the configure process as unfinished. 2. exec: Only --cross-execute - get the answer from cross-execute, an emulator (qemu) is used to run cross-compiled binaries. 3. both: Try the cross-answers file first, and if there is no corresponding answer, use cross-execute to get an answer, and add that answer to the file. The cross files in are all generated by qemu when the 'both' mode is enabled, and are placed in a common directory LAYERDIR/files/waf-cross-answers which is set as WAF_CROSS_ANSWERS_PATH in layer.conf of meta-oe, so that we don't have to put copies of them for each package (there are 5 packages inerit waf-samba for now) Signed-off-by: Jackie Huang Signed-off-by: Martin Jansa Signed-off-by: Joe MacDonald

waf-samba: enable parallel builds

2016-01-06T12:27:21+00:00

Instead of relying on sequencial waf build invoked by make, invoke waf as documented with default switch for building in parallel. Signed-off-by: Jens Rehsack Signed-off-by: Martin Jansa