All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zxing-cpp: drop opencv and qt dependencies
Date: Fri, 10 May 2024 23:35:00 +0200	[thread overview]
Message-ID: <20240510233500.49b47079@windsurf> (raw)
In-Reply-To: <20240307102535.20447-1-fontaine.fabrice@gmail.com>

On Thu,  7 Mar 2024 11:25:35 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> opencv and qt handling can be dropped since switch to an active fork in
> commit 456a7398316655ad0b669635f580e4887c24a700 as they are only used
> when examples are enabled resulting in the following warning:
> 
> CMake Warning:
>   Manually-specified variables were not used by the project:
> 
>     BUILD_DOC
>     BUILD_DOCS
>     BUILD_EXAMPLE
>     BUILD_TEST
>     BUILD_TESTING
>     BUILD_TESTS
>     CMAKE_DISABLE_FIND_PACKAGE_OpenCV
>     CMAKE_DISABLE_FIND_PACKAGE_Qt5
> 
> While at it, also drop BUILD_EXAMPLES which is already passed by
> pkg-cmake.mk
> 
> Fixes: 456a7398316655ad0b669635f580e4887c24a700
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/zxing-cpp/zxing-cpp.mk | 26 --------------------------
>  1 file changed, 26 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-10 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 10:25 [Buildroot] [PATCH 1/1] package/zxing-cpp: drop opencv and qt dependencies Fabrice Fontaine
2024-05-10 21:35 ` Thomas Petazzoni via buildroot [this message]
2024-06-08  7:27 ` Peter Korsgaard

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=20240510233500.49b47079@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.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 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.