linux/meta-openembedded.git/meta-oe/classes, branch pyro-nfvaccess

meson.bbclass: Use the correct C++ compiler when cross compiling

2017-03-16T22:32:40+00:00

Signed-off-by: Martin Jansa

meson.bbclass: Support building for native

2017-03-16T22:32:40+00:00

Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

meson.bbclass: Make changes to meson.build files trigger reconfiguration

2017-03-16T22:32:40+00:00

When externalsrc.bbclass is used, any changes to meson.build files should trigger do_configure to be re-run. Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

meson.bbclass: Add support for more standard installation directories

2017-03-16T22:32:40+00:00

A couple of more standard installation directories are supported with meson 0.37.1, so make sure they are configured. Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

gitver: fix try/except syntax for python3 support

2017-03-07T12:30:26+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

meson.bbclass: Add progress support for do_compile()

2017-03-07T12:30:26+00:00

ninja provides progress information when building so let's make use of it. Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

gitpkgv.bbclass: fix versioning with multiple repos

2017-02-22T12:16:48+00:00

gitpkgv class is supposed to use SRCREV_FORMAT variable to define how to smoosh together revision info from multiple repos that are used in a single recipe. It is incorrectly repeating the rev hash for the first repo instead of including the rev from each listed repo. Example: SRC_URI = "git://some-server/purple.git;destsuffix=git/purple;name=purple" SRC_URI += "git://other-server/blue.git;destsuffix=git/blue;name=blue" SRCREV_purple = "${AUTOREV}" SRCREV_blue = "${AUTOREV}" SRCREV_FORMAT = "purple_blue" Suppose gitpkgv calculates "67+ea121ea" for purple repo, and "123+feef001" for blue repo. This should result in a package version with them joined together like so: "67+ea121ea_123+feef001" It didn't. Instead the git hash part for the first repo got repeated: "67+ea121ea_123+ea121ea" Fix this by looking in the right place for the git revisions of 2nd (and following) repos when assembling the full version string. Signed-off-by: S. Lockwood-Childs Signed-off-by: Martin Jansa

meson.bbclass: Add meson.bbclass

2017-02-20T10:50:12+00:00

Add a class for packages that uses the meson build system. Meson uses a cross-file that contain needed tools and information about the host and target system. Such a file will be created in {WORKDIR}. Meson only allows installation directories to be specified as relative to prefix, except for sysconfdir, which can be absolute. This patch is based on a prototype patch by Ross Burton . Signed-off-by: Linus Svensson Signed-off-by: Martin Jansa

remove True option to getVar calls

2016-12-02T08:16:17+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ Signed-off-by: Joshua Lock

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