From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/freeswitch: select OpenCV modules needed for mod_cv
Date: Tue, 19 Apr 2016 21:05:22 +0200 [thread overview]
Message-ID: <20160419210522.1df89766@free-electrons.com> (raw)
In-Reply-To: <1461085245-30787-1-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Tue, 19 Apr 2016 19:00:45 +0200, Bernd Kuhls wrote:
> diff --git a/package/freeswitch/Config.in b/package/freeswitch/Config.in
> index 1350b2b..cef3fd4 100644
> --- a/package/freeswitch/Config.in
> +++ b/package/freeswitch/Config.in
> @@ -7,6 +7,17 @@ menuconfig BR2_PACKAGE_FREESWITCH
> depends on BR2_USE_WCHAR # libuuid
> select BR2_PACKAGE_LIBCURL
> select BR2_PACKAGE_JPEG
> + # src/mod/applications/mod_cv/mod_cv.cpp includes cv.h
> + select BR2_PACKAGE_OPENCV_LIB_CALIB3D if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_CONTRIB if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_FEATURES2D if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_FLANN if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_IMGPROC if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_LEGACY if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_OBJDETECT if BR2_PACKAGE_OPENCV
> + select BR2_PACKAGE_OPENCV_LIB_VIDEO if BR2_PACKAGE_OPENCV
> + # src/mod/applications/mod_cv/mod_cv.cpp includes highgui.h
> + select BR2_PACKAGE_OPENCV_LIB_HIGHGUI if BR2_PACKAGE_OPENCV
Now that inter-module dependencies are properly handled in opencv.mk,
why do we have to do all of this?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-19 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 17:00 [Buildroot] [PATCH v4 1/1] package/freeswitch: select OpenCV modules needed for mod_cv Bernd Kuhls
2016-04-19 19:05 ` Thomas Petazzoni [this message]
2016-04-19 20:08 ` Bernd Kuhls
2016-04-20 11:12 ` Samuel Martin
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=20160419210522.1df89766@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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