From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] opencv: always enable opencv_core module when opencv is enabled
Date: Sun, 16 Feb 2014 09:18:07 +0100 [thread overview]
Message-ID: <87vbwfii80.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1392502403-19701-3-git-send-email-s.martin49@gmail.com> (Samuel Martin's message of "Sat, 15 Feb 2014 23:13:23 +0100")
>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:
> It does not make much sense enabling opencv without its core module.
> This configuration leads to build nothing (since all modules depend on
> the core one), but install the configuration files (*.pc and *.cmake)
> anyway.
> This absurd situation may break the build-system of other packages
> that would correctly find the *.pc (but does not check for the modules
> they actually use), but would not build because of missing headers and
> libraries.
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-16 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 22:13 [Buildroot] [PATCH 0/2] vlc autobuild fixes and opencv modules mess? Samuel Martin
2014-02-15 22:13 ` [Buildroot] [PATCH 1/2] vlc: explicitly disable opencv support Samuel Martin
2014-02-16 8:17 ` Peter Korsgaard
2014-02-16 9:14 ` Samuel Martin
2014-02-17 8:02 ` Peter Korsgaard
2014-02-15 22:13 ` [Buildroot] [PATCH 2/2] opencv: always enable opencv_core module when opencv is enabled Samuel Martin
2014-02-16 8:18 ` Peter Korsgaard [this message]
2014-02-16 8:14 ` [Buildroot] [PATCH 0/2] vlc autobuild fixes and opencv modules mess? 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=87vbwfii80.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 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.