From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>, meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago][master][PATCH] kms++: Restore pybind11 support
Date: Thu, 8 Jun 2023 14:57:19 -0400 [thread overview]
Message-ID: <20230608185719.GC9226@denix.org> (raw)
In-Reply-To: <20230608183641.30832-1-reatmon@ti.com>
On Thu, Jun 08, 2023 at 01:36:41PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> Having this turned off is causing build errors and the errors that
> disabling pybind11 solved do not appear to be in master any more.
Yeah, I already had this change in my local queue for master, but have been
fighting other upstream issues...
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> meta-arago-extras/recipes-graphics/kms++/kms++_git.bb | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta-arago-extras/recipes-graphics/kms++/kms++_git.bb b/meta-arago-extras/recipes-graphics/kms++/kms++_git.bb
> index eb39736c..56b83c7a 100644
> --- a/meta-arago-extras/recipes-graphics/kms++/kms++_git.bb
> +++ b/meta-arago-extras/recipes-graphics/kms++/kms++_git.bb
> @@ -12,9 +12,8 @@ SRCREV = "5afc8d918f2c084acd65027604868dfde43395cf"
>
> DEPENDS = "drm fmt"
>
> -# New meson build system fails to find pybind11 in sysroot, disable for now
> -#DEPENDS += "python3-pybind11"
> -#EXTRA_OEMESON = "-Dsystem-pybind11=enabled"
> +DEPENDS += "python3-pybind11"
> +EXTRA_OEMESON = "-Dsystem-pybind11=enabled"
>
> PACKAGES =+ "${PN}-python"
next prev parent reply other threads:[~2023-06-08 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 18:36 [meta-arago][master][PATCH] kms++: Restore pybind11 support Ryan Eatmon
2023-06-08 18:57 ` Denys Dmytriyenko [this message]
2023-06-08 19:39 ` Ryan Eatmon
2023-06-08 20:49 ` Denys Dmytriyenko
2023-06-08 21:03 ` Ryan Eatmon
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=20230608185719.GC9226@denix.org \
--to=denis@denix.org \
--cc=meta-arago@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
/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.