From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] QT embedded working with Xorg?
Date: Thu, 01 Apr 2010 15:42:31 +0100 [thread overview]
Message-ID: <4BB4B0D7.4080002@carallon.com> (raw)
In-Reply-To: <4BB20147.50404@terawatt.fr>
On 30/03/2010 14:48, Damien Borie wrote:
> Hi,
>
> Thank you for your answer.
> If you can send it it's great. But maybe you can first say me what the
> modifications are?
> Modifying some line in configure file may be sufficient for some test?
> I noticed an option PLATFORM_X11...
> I could always make it cleaner when you send your clean patch but if
> there is only a few things to change I can do it dirtily for now and
> continue working.
Damien,
Attached is my patch to get this working. he main thing to do is to
trick the build into thinking it is doing a cross compile even though it
is building for XOrg. Although not officially support the Trolltech guys
confirmed that it should work.
There are various bits i the patch you may not like, not least that it
is setup for a commercial Qt license.
Will.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: qt-x11.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100401/60f79536/attachment-0001.diff>
next prev parent reply other threads:[~2010-04-01 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 12:27 [Buildroot] init segfaults when compiled with glibc Sasha Sirotkin
2010-03-30 13:11 ` [Buildroot] QT embedded working with Xorg? Damien Borie
2010-03-30 13:18 ` William Wagner
2010-03-30 13:48 ` Damien Borie
2010-04-01 14:42 ` Will Wagner [this message]
2010-04-01 15:21 ` Damien Borie
2010-04-02 11:49 ` Damien Borie
2010-04-03 14:30 ` Allan Clark
2010-04-05 10:33 ` Paul Jones
2010-04-05 18:15 ` Will Wagner
2010-04-05 21:34 ` Paul Jones
2010-03-30 13:20 ` [Buildroot] init segfaults when compiled with glibc Yann E. MORIN
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=4BB4B0D7.4080002@carallon.com \
--to=will_wagner@carallon.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