[webkit-dev] Moving away from qmake
mike.emmel at gmail.com
Mon Nov 12 09:57:11 PST 2007
On Nov 12, 2007 2:48 AM, Mike Hommey <mh+webkit at glandium.org> wrote:
> On Mon, Nov 12, 2007 at 03:34:48AM +0000, Alp Toker <alp at atoker.com> wrote:
> > An unforeseen benefit of the new build system is that it is modular,
> > rather than monolithic, and has no dependency on GLib/GTK+ or any other
> > as a standalone scripting engine independently of WebKit.
This is primarily I think from the use of QString internally in jscore.
I think the answer is a wtf/platfrom that contains at least the string handling.
This could have a platform independent version and optional platform
There is quit a bit of code in platform that has little to do with a
webbrowser and if pure cross
platform version are provided I think its useful in a wtf/platform
seems to have a lot of code that could be re factored to share a core
library with WebKit.
and even Timer although that probably cannot be done platform
independent without threads
Some of this could even benefit from using the JS gc.
Netscape has nspr Apache apr, Gtk has glib. So this sort of library
seems to arise often.
> built for the Qt port or the Gtk+ port, so it couldn't be shared between
> both, which is pretty sad, actually.
> As for switching away from qmake, I'm all for it, though I have no problem
> having to use qmake for the Gtk+ port, since I'm already building both Qt
> and Gtk+ ports in one pass for the Debian packages. I'll only add this: it
> would be nice to avoid linking to indirectly used libraries where possible,
> though it may be challenging. (I'm using -Wl,--as-needed for that matter)
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev