Alp Toker wrote:
you have to build the whole of Qt just to get qmake, which takes over an
hour and almost a gigabyte of disk space for me. That's at least 5 times
as long as it takes to build the whole of JavaScriptCore, WebCore and
WebKit.
Just to set the record straight, it turned out my bad
On Nov 16, 2007, at 12:58 PM, Alp Toker wrote:
Alp Toker wrote:
you have to build the whole of Qt just to get qmake, which takes
over an
hour and almost a gigabyte of disk space for me. That's at least 5
times
as long as it takes to build the whole of JavaScriptCore, WebCore and
WebKit.
Steve Atkins wrote:
IIRC, the two issues were that qmake is time-consuming to build and
that the existing .pro files were not handling dependencies correctly.
Is the latter the only issue now, or were there other problems?
This probably reduces the urgency for change. I think we need to wait
Mike Emmel wrote:
Here is my autoconf build files
They are for my current projects but I think they could readily be
cleaned up to b used with the standard build.
I found that having a single Makefile did not incur any performance problems.
Mike, just had a look over this and it's looking
Yes I rewrote the Curl code to use the new callback api's so you can
use select in the main thread.
Also the Pleyo people have done some work I've not fully integrated so
their work is worth looking at.
I ran into some issues and dropped back for the time being to a full
load on each call. Its a
Mike Emmel wrote:
I refactored all the Unicode handling to run behind a abstract interface.
So no direct ICU calls.
Its a lot of little patches all over the place and a thankless job.
Its a lot of work so email me if your interested.
I was also looking at repacling icu with glib/pango.
Its
6 matches
Mail list logo
