From: Martin Jansa <martin.jansa@gmail.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v4 6/7] opencv: Fix build on x86 platform
Date: Thu, 31 Mar 2016 14:59:37 +0200 [thread overview]
Message-ID: <20160331125937.GC2540@jama> (raw)
In-Reply-To: <1459423593-4123-7-git-send-email-ricardo.ribalda@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On Thu, Mar 31, 2016 at 01:26:32PM +0200, Ricardo Ribalda Delgado wrote:
> OpenCV wrongly assumes that the X86 variable would be set on Intel 32
> bit architectures.
>
> This patch adds the missing definition on those cases.
>
> Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> ---
> meta-oe/recipes-support/opencv/opencv_3.1.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-oe/recipes-support/opencv/opencv_3.1.bb b/meta-oe/recipes-support/opencv/opencv_3.1.bb
> index 84a592799c0a..7f09168784d9 100644
> --- a/meta-oe/recipes-support/opencv/opencv_3.1.bb
> +++ b/meta-oe/recipes-support/opencv/opencv_3.1.bb
> @@ -41,6 +41,7 @@ EXTRA_OECMAKE = "-DPYTHON2_NUMPY_INCLUDE_DIRS:PATH=${STAGING_LIBDIR}/${PYTHON_DI
> ${@base_conditional("libdir", "/usr/lib64", "-DLIB_SUFFIX=64", "", d)} \
> ${@base_conditional("libdir", "/usr/lib32", "-DLIB_SUFFIX=32", "", d)} \
> "
> +EXTRA_OECMAKE_append_x86 += " -DX86=ON"
Please don't combine _append and +=. _append and leading space in value
(as you already have) is enough.
>
> PACKAGECONFIG ??= "eigen jpeg png tiff v4l libv4l gstreamer samples tbb \
> ${@bb.utils.contains("DISTRO_FEATURES", "x11", "gtk", "", d)} \
> --
> 2.8.0.rc3
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-03-31 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 11:26 [meta-oe][PATCH v4 0/7] OpenCV Update to 3.1 and remove blacklist Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 1/7] opencv: Fix use before set error on meta package Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 2/7] opencv: Update to version 3.1 Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 3/7] opencv: Fix pkg-config file Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 4/7] opencv: Add missing dependencies Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 5/7] opencv: Use pre-downloaded ipp Ricardo Ribalda Delgado
2016-03-31 12:58 ` Martin Jansa
2016-03-31 13:13 ` Ricardo Ribalda Delgado
2016-03-31 11:26 ` [meta-oe][PATCH v4 6/7] opencv: Fix build on x86 platform Ricardo Ribalda Delgado
2016-03-31 12:59 ` Martin Jansa [this message]
2016-03-31 11:26 ` [meta-oe][PATCH v4 7/7] opencv: Remove blacklist Ricardo Ribalda Delgado
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=20160331125937.GC2540@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ricardo.ribalda@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox