From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qextserialport: don't require Qt GUI module
Date: Fri, 16 Nov 2012 08:44:32 +0100 [thread overview]
Message-ID: <20121116084432.6dde4f80@skate> (raw)
In-Reply-To: <87k3tmysez.fsf@dell.be.48ers.dk>
On Fri, 16 Nov 2012 07:26:44 +0100, Peter Korsgaard wrote:
> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>
> Arnout> While we're at it, we could also throw out our patching of the
> Arnout> platform-specific qws config file: we are anyway replacing all
> Arnout> "interesting" variables with our own values, so all useful
> Arnout> content is thrown away. Instead, we could make our own spec
> Arnout> file that contains exactly what we need:
>
> Arnout> include(../../common/linux.conf)
> Arnout> include(../../common/gcc-base-unix.conf)
> Arnout> include(../../common/g++-unix.conf)
> Arnout> include(../../common/qws.conf)
> Arnout> <our stuff goes here>
> Arnout> load(qt_config)
>
> Arnout> What do you think?
>
> I'm no Qt expert, but it sounds sensible - Thomas?
I don't remember all the details of those spec files, but yes, it
sounds good.
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:[~2012-11-16 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 21:44 [Buildroot] [git commit] qextserialport: don't require Qt GUI module Peter Korsgaard
2012-11-15 23:54 ` Arnout Vandecappelle
2012-11-16 6:26 ` Peter Korsgaard
2012-11-16 7:44 ` Thomas Petazzoni [this message]
2013-02-07 7:00 ` Arnout Vandecappelle
2013-02-07 8:24 ` 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=20121116084432.6dde4f80@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 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.