From: "Khem Raj" <raj.khem@gmail.com>
To: "Christian B. Sørensen" <yocto@bsorensen.net>,
openembedded-devel@lists.openembedded.org
Cc: chbs@prevas.dk
Subject: Re: [oe] [meta-oe][PATCH v2] libgpiod: packageqa problem => static python lib to ${PN}-staticdev
Date: Mon, 22 Feb 2021 09:23:46 -0800 [thread overview]
Message-ID: <0e73645d-8853-8540-eaed-1efce51ed360@gmail.com> (raw)
In-Reply-To: <20210222083711.412474-1-yocto@bsorensen.net>
It does not apply on current master, please rebase and send again.
On 2/22/21 12:37 AM, Christian B. Sørensen wrote:
> Problem:
> QA Issue: non -staticdev package contains static .a library
>
> Reason:
> Both /usr/lib/python3.8/site-packages/gpiod.a and
> /usr/lib/python3.8/site-packages/gpiod.so are in ${PN}-python.
>
> Signed-off-by: Christian Bräuner Sørensen <yocto@bsorensen.net>
> ---
> meta-oe/recipes-support/libgpiod/libgpiod_1.4.5.bb | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-support/libgpiod/libgpiod_1.4.5.bb b/meta-oe/recipes-support/libgpiod/libgpiod_1.4.5.bb
> index aec50e7e6..96ed3f18f 100644
> --- a/meta-oe/recipes-support/libgpiod/libgpiod_1.4.5.bb
> +++ b/meta-oe/recipes-support/libgpiod/libgpiod_1.4.5.bb
> @@ -28,6 +28,7 @@ FILES_${PN}-tools = "${bindir}/*"
> FILES_libgpiodcxx = "${libdir}/libgpiodcxx.so.*"
>
> PACKAGES =+ "${PN}-python"
> -FILES_${PN}-python = "${PYTHON_SITEPACKAGES_DIR}"
> +FILES_${PN}-python = "${PYTHON_SITEPACKAGES_DIR}/*.so"
> +FILES_${PN}-staticdev += "${PYTHON_SITEPACKAGES_DIR}/*.a"
> RRECOMMENDS_PYTHON = "${@bb.utils.contains('PACKAGECONFIG', 'python3', '${PN}-python', '',d)}"
> RRECOMMENDS_${PN}-python += "${RRECOMMENDS_PYTHON}"
>
>
>
>
>
prev parent reply other threads:[~2021-02-22 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 8:37 [meta-oe][PATCH v2] libgpiod: packageqa problem => static python lib to ${PN}-staticdev Christian B. Sørensen
2021-02-22 17:23 ` 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=0e73645d-8853-8540-eaed-1efce51ed360@gmail.com \
--to=raj.khem@gmail.com \
--cc=chbs@prevas.dk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@bsorensen.net \
/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.