Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt QtUiTools
Date: Wed, 8 Sep 2010 12:29:51 +0200	[thread overview]
Message-ID: <20100908122951.5b2f9761@surf> (raw)
In-Reply-To: <AANLkTinS00d+cpiORtAghjVRibz+_3K5Zh1mWBzPBLbw@mail.gmail.com>

On Wed, 8 Sep 2010 09:58:50 +0100
mailing list <mailinglist@gatt.me> wrote:

> I've recently used the Qt build of buildroot and noticed that I
> couldn't use QUiLoader, I had to add "-make tools" to the configure
> line to compile the necessary libraries so that I could use these
> functions. I don't believe it affects the rootfs size (although I
> have to admit I didn't run a test), but the extra functionality gets
> compiled into the executable if i understand it correctly. It will
> however increase build time. No other libraries require copying
> across.
> 
> I was wondering if it would be worth adding this as an option to
> menuconfig so that it can be built if required.

I don't know what QtUiTools are, but if it's useful for you, it's
probably useful for others as well. So, yes, having this as a
menuconfig option makes sense.

Could you submit a patch that implements this ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-08 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  8:58 [Buildroot] Qt QtUiTools mailing list
2010-09-08 10:29 ` Thomas Petazzoni [this message]
2010-09-08 13:33   ` Andrew Gatt

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=20100908122951.5b2f9761@surf \
    --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