From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] libiio: Disable python support for determism
Date: Thu, 24 Oct 2019 09:10:34 +0100 [thread overview]
Message-ID: <CAMKF1sqpmTaLH+CzS1dQ7CRpP8qT+XdHBm_NAZDtVh-c2E+maQ@mail.gmail.com> (raw)
In-Reply-To: <20191023201407.14068-1-richard.purdie@linuxfoundation.org>
On Wed, Oct 23, 2019 at 9:14 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Recent cmake changes in OE-Core mean python is now detected from
> PATH. For determism, disable the python bindings to match
> previous behaviour.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta-oe/recipes-support/libiio/libiio_git.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-oe/recipes-support/libiio/libiio_git.bb b/meta-oe/recipes-support/libiio/libiio_git.bb
> index 4e57d5b77..63248b4e3 100644
> --- a/meta-oe/recipes-support/libiio/libiio_git.bb
> +++ b/meta-oe/recipes-support/libiio/libiio_git.bb
> @@ -22,6 +22,7 @@ DEPENDS = " \
> EXTRA_OECMAKE = " \
> -DCMAKE_BUILD_TYPE=RelWithDebInfo \
> -DUDEV_RULES_INSTALL_DIR=${nonarch_base_libdir}/udev/rules.d \
> + -DPYTHON_BINDINGS=OFF \
instead of disabling the bindings if we specify location to python
library and headers then it works
this is in effect after the cmake change
> ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '-DWITH_SYSTEMD=ON -DSYSTEMD_UNIT_INSTALL_DIR=${systemd_system_unitdir}', '', d)} \
> "
>
> --
> 2.20.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2019-10-24 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:14 [PATCH] libiio: Disable python support for determism Richard Purdie
2019-10-24 8:10 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMKF1sqpmTaLH+CzS1dQ7CRpP8qT+XdHBm_NAZDtVh-c2E+maQ@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.