From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qt{4, 5}: add an explicit choice to express Buildroot does not support their coexistence
Date: Sun, 7 Jul 2013 21:23:35 +0200 [thread overview]
Message-ID: <20130707212335.630a2d32@skate> (raw)
In-Reply-To: <CAHXCMMKx-vf9ZFRgzhj_bvYwbb2vHz3qQkC6ebgKqts_-v6-bA@mail.gmail.com>
Dear Samuel Martin,
On Sun, 7 Jul 2013 21:08:25 +0200, Samuel Martin wrote:
> I forgot to mention that using an explicit choice allow to get rid of
> the dependency between the
> Qt4 and Qt5 packages.
> So, for packages supporting both Qt4 and Qt5 (like OpenCV), it makes
> possible to handle the
> right dependency with no circular/recursive dependency in the Config.in files.
Can you give more details about this circular/recursive dependency
problem?
I'm not too enthusiastic about your PATCH 1/3, so I'd like to be sure
to completely understand what the problem is, and look at the different
possible solutions.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-07 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 18:44 [Buildroot] [PATCH 1/3] qt{4, 5}: add an explicit choice to express Buildroot does not support their coexistence Samuel Martin
2013-07-07 18:44 ` [Buildroot] [PATCH 2/3] manual: add faq entry explaining why Buildroot does not support Qt{4, 5} coexistence Samuel Martin
2013-07-07 18:44 ` [Buildroot] [PATCH 3/3] opencv: bump version to 2.4.6 Samuel Martin
2013-07-07 19:28 ` Thomas Petazzoni
2013-07-07 20:21 ` Samuel Martin
2013-07-07 19:08 ` [Buildroot] [PATCH 1/3] qt{4, 5}: add an explicit choice to express Buildroot does not support their coexistence Samuel Martin
2013-07-07 19:23 ` Thomas Petazzoni [this message]
2013-07-09 19:44 ` 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=20130707212335.630a2d32@skate \
--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