Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Cc: Francis Laniel <flaniel@linux.microsoft.com>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Samuel Martin <s.martin49@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/opencv4: add tbb support
Date: Thu, 21 Apr 2022 22:53:44 +0200	[thread overview]
Message-ID: <fa175e14-5389-c4e5-797d-fec78401afcf@mind.be> (raw)
In-Reply-To: <20220416210750.3065016-2-fontaine.fabrice@gmail.com>



On 16/04/2022 23:07, Fabrice Fontaine wrote:
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

  Applied to master, thanks.

  Regards,
  Arnout

> ---
>   package/opencv4/Config.in  | 14 ++++++++++++++
>   package/opencv4/opencv4.mk | 10 ++++++++--
>   2 files changed, 22 insertions(+), 2 deletions(-)
> 
> diff --git a/package/opencv4/Config.in b/package/opencv4/Config.in
> index 31c32385da..23d34a9d22 100644
> --- a/package/opencv4/Config.in
> +++ b/package/opencv4/Config.in
> @@ -309,6 +309,20 @@ config BR2_PACKAGE_OPENCV4_WITH_PROTOBUF
>   	help
>   	  Use shared protobuf from the target system.
>   
> +config BR2_PACKAGE_OPENCV4_WITH_TBB
> +	bool "tbb support"
> +	depends on !BR2_TOOLCHAIN_USES_UCLIBC # tbb
> +	depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735 # tbb
> +	select BR2_PACKAGE_TBB
> +	help
> +	  Use shared tbb from the target system.
> +
> +comment "tbb needs a glibc or musl toolchain"
> +	depends on BR2_TOOLCHAIN_USES_UCLIBC
> +
> +comment "tbb needs exception_ptr"
> +	depends on BR2_TOOLCHAIN_HAS_GCC_BUG_64735
> +
>   config BR2_PACKAGE_OPENCV4_WITH_TIFF
>   	bool "tiff support"
>   	select BR2_PACKAGE_TIFF
> diff --git a/package/opencv4/opencv4.mk b/package/opencv4/opencv4.mk
> index e75f7144de..0563026b18 100644
> --- a/package/opencv4/opencv4.mk
> +++ b/package/opencv4/opencv4.mk
> @@ -155,8 +155,7 @@ OPENCV4_CONF_OPTS += \
>   	-DBUILD_WITH_DYNAMIC_IPP=OFF \
>   	-DWITH_INTELPERC=OFF \
>   	-DWITH_IPP=OFF \
> -	-DWITH_IPP_A=OFF \
> -	-DWITH_TBB=OFF
> +	-DWITH_IPP_A=OFF
>   
>   # Smartek stuff
>   OPENCV4_CONF_OPTS += -DWITH_GIGEAPI=OFF
> @@ -313,6 +312,13 @@ else
>   OPENCV4_CONF_OPTS += -DWITH_QT=OFF
>   endif
>   
> +ifeq ($(BR2_PACKAGE_OPENCV4_WITH_TBB),y)
> +OPENCV4_CONF_OPTS += -DWITH_TBB=ON
> +OPENCV4_DEPENDENCIES += tbb
> +else
> +OPENCV4_CONF_OPTS += -DWITH_TBB=OFF
> +endif
> +
>   ifeq ($(BR2_PACKAGE_OPENCV4_WITH_TIFF),y)
>   OPENCV4_CONF_OPTS += -DWITH_TIFF=ON
>   OPENCV4_DEPENDENCIES += tiff
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-21 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 21:07 [Buildroot] [PATCH 1/2] package/tbb: bump to version 2021.5.0 Fabrice Fontaine
2022-04-16 21:07 ` [Buildroot] [PATCH 2/2] package/opencv4: add tbb support Fabrice Fontaine
2022-04-21 20:53   ` Arnout Vandecappelle [this message]
2022-04-19 16:32 ` [Buildroot] [PATCH 1/2] package/tbb: bump to version 2021.5.0 Francis Laniel
2022-04-19 20:48   ` Arnout Vandecappelle

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=fa175e14-5389-c4e5-797d-fec78401afcf@mind.be \
    --to=arnout@mind.be \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=flaniel@linux.microsoft.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=s.martin49@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