From: <kai.kang@windriver.com>
To: <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: [PATCH 2/2] opencv: correct subpackage name for multilib
Date: Wed, 12 Apr 2017 09:42:01 +0800 [thread overview]
Message-ID: <20170412014201.23476-3-kai.kang@windriver.com> (raw)
In-Reply-To: <20170412014201.23476-1-kai.kang@windriver.com>
From: Kai Kang <kai.kang@windriver.com>
Subpackage python3-${PN} is not right for multilib and it will be
extended to such as lib32-python3-lib32-opencv.
Replace PN with BPN to fix it.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
meta-oe/recipes-support/opencv/opencv_3.2.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-support/opencv/opencv_3.2.bb b/meta-oe/recipes-support/opencv/opencv_3.2.bb
index b5b4968..2cff212 100644
--- a/meta-oe/recipes-support/opencv/opencv_3.2.bb
+++ b/meta-oe/recipes-support/opencv/opencv_3.2.bb
@@ -97,8 +97,8 @@ TARGET_CC_ARCH += "-I${S}/include "
PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'samples', '${PN}-samples', '', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'oracle-java', '${PN}-java', '', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'java', '${PN}-java', '', d)} \
- ${@bb.utils.contains('PACKAGECONFIG', 'python2', 'python-${PN}', '', d)} \
- ${@bb.utils.contains('PACKAGECONFIG', 'python3', 'python3-${PN}', '', d)} \
+ ${@bb.utils.contains('PACKAGECONFIG', 'python2', 'python-${BPN}', '', d)} \
+ ${@bb.utils.contains('PACKAGECONFIG', 'python3', 'python3-${BPN}', '', d)} \
${PN}-apps"
python populate_packages_prepend () {
--
2.10.1
prev parent reply other threads:[~2017-04-12 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 1:41 [meta-oe][PATCH 0/2] V3: Fix gflags and opencv build errors for multilib kai.kang
2017-04-12 1:42 ` [PATCH 1/2] gflags: correct S and update library install directory kai.kang
2017-04-12 1:42 ` kai.kang [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=20170412014201.23476-3-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox