diff options
author | Mark Hatle <mark.hatle@windriver.com> | 2017-03-07 12:54:33 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-03-08 11:52:56 +0000 |
commit | fc6c81da79897c95a9c81960a1dee49517f2562a (patch) | |
tree | 01a121cc4584e11ebdc1fd542428d3a4de93b492 /meta/recipes-devtools/unifdef | |
parent | 07eca818019e1969c78afa8932f0e2cda1fc8e72 (diff) | |
download | poky-fc6c81da79897c95a9c81960a1dee49517f2562a.tar.gz |
gpgme: Fix issue building for the target
gpgme failed when configuring since you can only configure for one python
system at a time (via the inherits). So we need to have a PACKAGECONFIG
that defines which one [or neither] you want to use.
The prior pkgconfig patch introduced the usage of the variable PKG_CONFIG,
which is not defined anywhere. Define this.
When building the python module, we can not call gpg-error-config, so we
need to find an alternative way of finding the information the setup.py.in
requires. (In this case, it's easy to just use the environment
STAGING_INCDIR.)
(From OE-Core rev: 839d6f124c2761194c868cf5597e1aa96571e1ca)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/unifdef')
0 files changed, 0 insertions, 0 deletions