Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Gatt <mailinglist@gatt.me>
To: buildroot@busybox.net
Subject: [Buildroot] Qt QtUiTools
Date: Wed, 08 Sep 2010 14:33:34 +0100	[thread overview]
Message-ID: <4C8790AE.50000@gatt.me> (raw)
In-Reply-To: <20100908122951.5b2f9761@surf>

>
>> 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 ?
Please find attached the two patches for the "buildroot/packages/qt/" 
folder. I've not submitted a patch here before so please let me know if 
these are in the correct format etc.

Andrew

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Config.in_patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100908/0e0e0814/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: qt.mk_patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100908/0e0e0814/attachment-0001.ksh>

      reply	other threads:[~2010-09-08 13:33 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
2010-09-08 13:33   ` Andrew Gatt [this message]

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=4C8790AE.50000@gatt.me \
    --to=mailinglist@gatt.me \
    --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