All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] QT embedded working with Xorg?
Date: Mon, 05 Apr 2010 19:15:48 +0100	[thread overview]
Message-ID: <4BBA28D4.2040702@carallon.com> (raw)
In-Reply-To: <4BB9BC7C.4030404@iwtech.com.au>

On 05/04/2010 11:33, Paul Jones wrote:
> On 04/02/10 22:49, Damien Borie wrote:
>    
>> Hi,
>>
>> It's working fine! I only changed X11-commercial to X11-opensource and
>> it's ok. I got problems with font or encoding but it will be cleared
>> soon I think.
>> Thank you, your patch was very useful.
>>      
> What arch are you building for? I'm building for ARM and I'm getting
> build errors.
>
>    
If you are using the patch I submitted to the list without modification 
then i don't think it will work. I had hard coded into that patch that 
Qt was being built for x86 (also being built on x64 machine). The patch 
was not meant to be for the general case and would need more work for 
that. If there is interest I will look at doing a better patch for 
submission.

Will

  reply	other threads:[~2010-04-05 18:15 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
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 [this message]
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=4BBA28D4.2040702@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 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.