Hi!
On Jul 11, 2009, at 1:43 PM, Ishikawa wrote:
I was able to build cairo-webkit.dll on Win Vista Home with VS2005
Express.
2009/7/10
However, some trouble was found.
Yeah, there are a couple of remainig rough spots.
By the way, in the future These kinds of messages should be sent to
That's a good point... Unfortunately, the integration builder really needs
to see HEAD chromium since we're frequently rolling DEPS to pick up the
latest WebKit tip-of-tree. Seeing any bustage related to such updates is
important. Perhaps a LKGR bot could be useful as an additional bot.
-Darin
I was able to build cairo-webkit.dll on Win Vista Home with VS2005 Express.
2009/7/10
However, some trouble was found.
1.Compile Error.
[Cairo Build: WebFrame.cpp fails to compile]
http://www.nabble.com/Cairo-Build%3A-WebFrame.cpp-fails-to-compile-tp24032535p24032535.html
Therefore, I patched W
On Jul 11, 2009, at 9:39 AM, Darin Adler wrote:
On Jul 10, 2009, at 4:23 PM, Maciej Stachowiak wrote:
Perhaps we should make update-webkit (or some new wrapper type
tool) run resolve-ChangeLogs automatically.
Dave Kilzer had the same idea when he created resolve-ChangeLogs, so
update-web
Hi Jeremy,
On Jul 10, 2009, at 6:54 PM, Jeremy Orlow wrote:
On Fri, Jul 10, 2009 at 6:26 PM, Kevin Ollivier > wrote:
Hi Jeremy,
On Jul 10, 2009, at 3:03 PM, Jeremy Orlow wrote:
[snip]
Your argument makes sense if WebKit is only built for one platform/
build-system. Unfortunately it's not.
On Jul 10, 2009, at 4:23 PM, Maciej Stachowiak wrote:
Perhaps we should make update-webkit (or some new wrapper type tool)
run resolve-ChangeLogs automatically.
Dave Kilzer had the same idea when he created resolve-ChangeLogs, so
update-webkit does run resolve-ChangeLogs automatically. See
Maciej,
You had mentioned that there were a couple people at Apple the
intended to start working on WebSockets soonish, is that still the
plan? If so, who should be CCed on the appropriate bugs?
Ukai-san, I think the next step here it to file a bug at
bugs.webkit.org and to start sending patches.
An hypothetical chromium builder should sync to
http://chromium-status.appspot.com/lkgr instead of HEAD. That'd fix most of
the "builder failed to compile because chromium tree is broken".
lkgr stands for *last known good revision* in its weakest meaning. If
curious, more info at
http://dev.chromi
Hello.
I have a problem compiling the latest GIT version of webkit. My system
is ArchLinux 64-bit and gcc 4.4. My configure looks like this:
./configure --prefix=/usr --enable-debug --disable-optimizations
When compiling webkit I got the following error:
-
/usr/bin/ld: ./.libs/li
9 matches
Mail list logo
