The unfortunate truth is that the current state of Windows port is not
good i.e. it was not kept up-to-date with changes to WebKit. I got it
compiling few months back but I didn't submit the fixes because it was
crashing and I couldn't figure out why. There are patches in bugzilla
that claim to
On 2/24/07, Nikolas Zimmermann [EMAIL PROTECTED] wrote:
2) Additional testing
* Fuzz-test for custom parsers - the biggest security risk is
buffer overruns in some of the custom parsers, so we'd like to
develop a fuzz-testing tool for attributes that trigger these, and
Speaking purely for myself, not the webkit team...
Fixing compilation issues due to refactoring changes is trivial. In
the past I can recall only one issue that required me to spend
non-trivial amount of time figuring out a fix for a change due to
refactoring. So a branch doesn't make a
On 2/21/07, Maciej Stachowiak [EMAIL PROTECTED] wrote:
Have you tried using a static checker for these?
We're looking into applying a static checker for all of WebKit; we
need to work out the logistics, to make sure there are up-to-date
results regularly available to the community.
I'd love to see the gdk work mature into a traditional gtk port.
I'm currently working on that. The trunk now builds for gtk.
I have quite a bit of cairo/svg and curl work I've done since my last
commits to webkit that should be integrated back into the main tree
and if someone takes
Current svn gdk build works. Here's a script I use to do a full build:
[EMAIL PROTECTED]:~/src/webkit-tot$ more ./gdk-rebuild.sh
Currently it probably won't compile anyway due to recent changes, but...
First, make sure that you do svn co under cygwin shell in order to
get files with unix-style line-ending - last time I've tried and
didn't do it, perl scripts wouldn't work.
It's also possible you're not running from
Mail list logo