Stubbing out the headers in an easy way. I've still not updated my build
machine due to this.
But it's generally hard to build w/o signing up for an apple id since the
latest XCode generally requires one.
-eric
On Tue, Nov 16, 2010 at 9:10 PM, Luke Macpherson wrote:
> This is preventing me fr
Hi Hajime,
On Nov 16, 2010, at 8:52 PM, Hajime Morita wrote:
> Hi WebKit folks,
>
> I'm thinking about porting Hunspell-based spellchecking code
> from Chromium to WebKit/WebCore.
>
> Although it's unclear whether the porting is feasible, I'd like to
> hear how much interest is there from other
This is preventing me from building. Is there a solution that doesn't
require signing up for an Apple ID?
On Fri, Oct 29, 2010 at 3:17 AM, Tony Gentilcore wrote:
>
>
> On Wed, Oct 27, 2010 at 10:11 PM, Eric Seidel wrote:
>>
>> Can we just include the headers in WebKit?
>>
>> Or find some way to
Hi WebKit folks,
I'm thinking about porting Hunspell-based spellchecking code
from Chromium to WebKit/WebCore.
Although it's unclear whether the porting is feasible, I'd like to
hear how much interest is there from other ports before starting
actual work.
Because the main goal is to make spellch
Hi,
I am trying to build the WebKit Cairo port but running into some issues. I
fixed my local compiler errors(mostly by tweaking code to avoid the errors) but
now running into a crash that looks like something inside CFLite.dll.
I built as per instructions here -
http://trac.webkit.org/wiki/Bu
On 11/16/2010 6:42 AM, Thomas Brodt wrote:
The buildbot for the wincairo port is running again, thanks to whoever
did repair it (Brent?).
But the build fails again, as before when it went offline.
There are errors installing the new WebKitSupportLibrary:
cp: cannot create regular file
`"D:/Pr
On Nov 10, 2010, at 11:29 , Maciej Stachowiak wrote:
>
> The first thing we should figure out is whether XSLT 2.0 is something we even
> want to implement. If it's not backwards compatible with XSLT 1.0 and other
> browsers are not planning on implementing it, then it's a significant risk to
[...]
>> (I wrote the XPath, XQuery and XSL-T code and mentored the Schema code.
>> However, I'm no longer employed by Nokia.)
>>
>
> That's good to know!
>
> Have the compliance tests for XSLT 2.0 and XQuery been run?
Yes, the details are at:
http://doc.qt.nokia.com/4.7/xmlprocessing.html#f
8 matches
Mail list logo
