Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/webkit
Date: Wed, 28 Jan 2009 09:30:29 +0100	[thread overview]
Message-ID: <877i4fx26y.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090128091937.6db2ef12@hcegtvedt> (Hans-Christian Egtvedt's message of "Wed\, 28 Jan 2009 09\:19\:37 +0100")

>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:

 >> Sure? Ever tried compiling it without WCHAR? ;)
 >> 

 Hans-Christian> Qt uses webkit, and AFAIK compiles without WCHAR enabled.

How? Without using libicu? I know close to nothing about webkit.

 Hans-Christian> FWIW webkit in Qt 4.5 builds with the AVR32 toolchain
 Hans-Christian> (gcc 4.2.2 + vendor patch).

The webkit version we have in BR (some svn nightly) most likely also
built at some time, but I know from other C++ projects that gcc 4.3.x
cleaned up quite some stuff and got more strict.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-28  8:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 15:10 [Buildroot] svn commit: trunk/buildroot/package/webkit jacmet at uclibc.org
2009-01-28  7:10 ` Hans-Christian Egtvedt
2009-01-28  7:58   ` Peter Korsgaard
2009-01-28  8:06     ` Hans-Christian Egtvedt
2009-01-28  8:14       ` Peter Korsgaard
2009-01-28  8:19         ` Hans-Christian Egtvedt
2009-01-28  8:30           ` Peter Korsgaard [this message]
2009-01-28  8:39             ` Hans-Christian Egtvedt
  -- strict thread matches above, loose matches on Subject: below --
2009-01-27 15:02 jacmet at uclibc.org
2009-01-27 15:02 jacmet at uclibc.org
2009-01-23 17:49 ulf at uclibc.org
2009-01-27  0:27 ` Hamish Moffatt
2009-01-27  8:25   ` Daniel Laird
2009-01-27  8:57     ` Peter Korsgaard
2009-01-27 10:15       ` Daniel James Laird
2009-01-27 15:06         ` Peter Korsgaard
2008-04-24 13:22 ninevoltz at uclibc.org

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=877i4fx26y.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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