[webkit-dev] WebKit and Windows/Cygwin

Frank.Lautenbach at softechnics.com Frank.Lautenbach at softechnics.com
Tue Sep 9 12:17:46 PDT 2008


That's interesting because on a Windows machine you have to use cygwin,
but cygwin supports qt3 only. I take it from your remark that qt4 is
required. Therefore, it is not possible build for Windows. (By the way,
I don't know how the QTDIR environment variable got set. The cygwin
installation did not set it because I have another machine with cygwin
that doesn't have that environment variable.)

So, you're saying I can force an Apple build, but that does me no good
because I have a Windows machine.


-----Original Message-----
From: Mark Rowe [mailto:mrowe at apple.com] 
Sent: Tuesday, September 09, 2008 2:43 PM
To: Lautenbach Frank SOFTECHNICS
Cc: darin at apple.com; webkit-dev at lists.webkit.org
Subject: Re: [webkit-dev] WebKit and Windows/Cygwin

On Sep 9, 2008, at 11:02 AM, Frank.Lautenbach at softechnics.com wrote:

> Apparently that's not what I want then. It is still curious that I  
> can't
> seem to build it under cygwin (as per the instructions.) Perhaps  
> this is
> due to the fact that after I got the source, the update command  
> doesn't
> succeed. It always fails at some point, so maybe the tree is not being
> updated completely for a proper build.

The error mentioned in your initial email indicates that the build- 
webkit script had detected that you were attempting to build the Qt  
Windows port rather than the Apple Windows port.  It failed to build  
the Qt Windows port due to having an older version of Qt installed  
than what WebKit requires to build.  You can force it to build the  
Apple Windows port, which the instructions on webkit.org are aiming to  
build, by unsetting the QTDIR environment variable before running  

> I did download the nightly build the other day and noticed that after
> all was said and done, running it simply called Safari.exe (which I  
> had
> to install) and passed it a command line parameter pointing to the
> downloaded webkit. I take it this is calling Safari and over-riding  
> the
> default engine Safari.exe was built with using the one referenced on  
> the
> command line. In other words, this allows for customization of
> Safari.exe?

Safari is set up to allow an updated version of WebKit to be used with  
it, yes.  This is for the purpose of testing new WebKit versions and  
is not a supported mechanism for extending Safari.exe.

Kind regards,

Mark Rowe

More information about the webkit-dev mailing list