Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/python-imutils: new package
Date: Wed, 5 Feb 2020 16:20:13 +0100	[thread overview]
Message-ID: <20200205162013.2749e009@windsurf> (raw)
In-Reply-To: <20190802144503.23601-1-alexandre.payen@smile.fr>

Hello Alexandre,

On Fri,  2 Aug 2019 16:45:03 +0200
Aalx <alexandre.payen@smile.fr> wrote:

> diff --git a/package/python-imutils/Config.in b/package/python-imutils/Config.in
> new file mode 100644
> index 0000000000..0c8ffbda56
> --- /dev/null
> +++ b/package/python-imutils/Config.in
> @@ -0,0 +1,36 @@
> +config BR2_PACKAGE_PYTHON_IMUTILS
> +	bool "python-imutils"
> +	depends on BR2_PACKAGE_PYTHON_NUMPY_ARCH_SUPPORTS # python-scipy
> +	depends on BR2_PACKAGE_PYTHON3 # python-scipy
> +	depends on BR2_TOOLCHAIN_HAS_FORTRAN # python-scipy
> +	depends on BR2_TOOLCHAIN_HAS_ATOMIC # opencv3
> +	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # opencv3
> +	depends on BR2_INSTALL_LIBSTDCPP # opencv3
> +	depends on BR2_USE_WCHAR # opencv3
> +	depends on !BR2_STATIC_LIBS  # opencv3
> +	depends on !BR2_PACKAGE_OPENCV # opencv3
> +	depends on BR2_PACKAGE_OPENCV3

If you "depends on BR2_PACKAGE_OPENCV3", there is no need to replicate
all the dependencies of opencv3 inside this package.

> +	select BR2_PACKAGE_PYTHON_SCIPY

We don't have this package in Buildroot, this needs to be added before
we can merge python-imutils.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-02-05 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 14:45 [Buildroot] [PATCH v3] package/python-imutils: new package Aalx
2020-02-05 15:20 ` Thomas Petazzoni [this message]
2020-02-05 15:25   ` Alexandre PAYEN
2020-09-23  5:04   ` Bernd Kuhls
     [not found] ` <bc9d03e2-428c-9c39-f750-cc0c97213643@t-online.de>
2020-09-23  6:56   ` Thomas Petazzoni

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=20200205162013.2749e009@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox