From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] WebkitGtk upgradation
Date: Thu, 28 Feb 2013 13:23:32 +0100 [thread overview]
Message-ID: <87ehg04ofv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130228122855.6ceb26ce@skate> (Thomas Petazzoni's message of "Thu, 28 Feb 2013 12:28:55 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Dear Will Newton,
Thomas> On Thu, 28 Feb 2013 10:22:27 +0000, Will Newton wrote:
>> As far as I can tell DirectFB is not really supported any more. If I
>> remember correctly the current WebKit in buildroot will build with
>> GTK+/DirectFB but will crash on startup. The crash is fairly easy to
>> work around but I think is a symptom of the fact that no one is
>> running with this setup.
>>
>> Newer versions of GTK+ removed the DirectFB backend so it may have to
>> be removed from buildroot in the future too.
Thomas> My feeling is also that the DirectFB backend of Gtk has never been
Thomas> seriously maintained over time. There are from time to time some people
Thomas> who fix the issues, but then it goes on unmaintained for a number of
Thomas> months/years, during which it slowly degrades into an unusable state.
Thomas> I would therefore suggest that Buildroot follows upstream: get
Thomas> rid of the DirectFB backend. If anyone really wants the
Thomas> DirectFB backend in Gtk, then it should be fixed upstream. But
Thomas> I don't think it should force Buildroot users to stay with old
Thomas> Webkit/Gtk because of this.
Agreed. I've added a comment for 2013.02 to warn users that it is
deprecated:
http://git.buildroot.net/buildroot/commit/?id=0e0e42176d4a46515aff577d9702d91208e27c5d
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-28 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 5:53 [Buildroot] WebkitGtk upgradation Bhupal Singh
2013-02-28 7:45 ` Stephan Hoffmann
2013-02-28 8:52 ` Bhupal Singh
2013-02-28 10:22 ` Will Newton
2013-02-28 11:28 ` Thomas Petazzoni
2013-02-28 11:36 ` Gustavo Zacarias
2013-02-28 12:23 ` Peter Korsgaard [this message]
2013-03-06 4:42 ` Bhupal Singh
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=87ehg04ofv.fsf@dell.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