As long as the newly imported tests use relative URLs, alias may be used as
a workaround. I will give it a try.
Bug entry is at https://bugs.webkit.org/show_bug.cgi?id=125339
Any further help appreciated,
Youenn
2013/12/6 Darin Adler da...@apple.com
If that's really ends up being super hard
Hi,
Perhaps that webkit-...@lists.webkit.org is more suitable for this question
(as this is related to the gtk port)
Romain
2013/12/6 larry x.wang larry.x.w...@oracle.com
How can I install a specific version of webkitgtk? ie 1.9.X
in the download tar,When I extract the tar package,the
HI Geoffrey,
Thanks a lot for your answer.
After studying the code a bit, it appears that my app is sharing a
JSGlobalContext with others. This context is, by design, never destroyed.
I read the WebKit JavaScript core documentation (
The way I got around this when I was first working on it was to simply map
imported/w3c onto a subdirectory of the document root in apache; it's a two
line change.
For some time I've toyed with the idea of changing the DocumentRoot to just
be LayoutTests/, so that any test could be run over http
Hi Everyone,
We are working hard to move WebKit toward stronger adoption of C++11 features,
such as variadic templates, ranged for-loops, and initializer lists.
Unfortunately, this effort has been hampered by the small subset of C++11
features available in Visual Studio 2010.
You can get a
That is awesome. Great work!
Benjamin
On 12/6/13, 2:53 PM, Brent Fulgham wrote:
Hi Everyone,
We are working hard to move WebKit toward stronger adoption of C++11
features, such as variadic templates, ranged for-loops, and initializer
lists. Unfortunately, this effort has been hampered by the
Wonderful ! C++11 is a great norm, good news ! ;)
Le 6 déc. 2013 à 23:53, Brent Fulgham bfulg...@apple.com a écrit :
Hi Everyone,
We are working hard to move WebKit toward stronger adoption of C++11
features, such as variadic templates, ranged for-loops, and initializer
lists. Unfortunately,
Is there any advantage of VS2013 instead of VS2012? I've been using VS2012
for a while, and it works fine. It also has the C++11 features we want to
use. Staying one version behind the latest usually prevents updates from
breaking things.
Alex Christensen
On Fri, Dec 6, 2013 at 3:53 PM,
Hi Alex,
There are a few items missing from VS2012 (see
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx) that we are
already using in the Mac-specific source code:
1. Variadic Templates
2. Initializer Lists
3. Explicit conversion operators
4. Deleted functions
None of those
On Dec 6, 2013, at 4:15 PM, Brent Fulgham bfulg...@apple.com wrote:
Hi Alex,
There are a few items missing from VS2012 (see
http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx) that we are
already using in the Mac-specific source code:
1. Variadic Templates
2. Initializer
You talked me into it! I'll go get VS2013. I hope it crashes less than
VS2010, too.
Alex
On Fri, Dec 6, 2013 at 5:26 PM, Anders Carlsson ander...@apple.com wrote:
On Dec 6, 2013, at 4:15 PM, Brent Fulgham bfulg...@apple.com wrote:
Hi Alex,
There are a few items missing from VS2012 (see
Actually, despite similarities with WIN32 situation, this patch seemed to
be useless in our case. I managed to
go one step beyond by adding (sadly but surely ;-) Glibutilies.o +
GOwnPtr.o + GrefPtr.o in WebCore.xcodeproj
manually by XCODE to force LINK with these file objects... That are
generated
This is great news !! Looking forward to see WinCairo on VS2013 :) Good
Work guys !
Regards,
Mital Vora.
On Sat, Dec 7, 2013 at 4:23 AM, Brent Fulgham bfulg...@apple.com wrote:
Hi Everyone,
We are working hard to move WebKit toward stronger adoption of C++11
features, such as variadic
13 matches
Mail list logo
