Hi everyone, I’ve been reviewing some of the setup and reliability problems with our Windows builders, and have discovered that there are a number of challenges to getting a working Cygwin environment for building WebKit:
You must use very specific versions of some Cygwin tools: 1. curl version 7.33.0: If not, you get certificate errors when attempting to retrieve WebKitAuxilliaryLibraries.zip from apple.com. Cygwin attempts to install 7.34.0, which will cause failures during “update-webkit”. You must manually select the 7.33 build. 2. Python version 2.6.8: If not, you get errors indicating “Invalid Python installation: unable to open ‘/cygdrive/c/Cygwin/include/python2.7/pyconfig.h”. This seems to be a regression since 2.6.8. Again, Cygwin tries to upgrade you to 2.7.3 every time you run the Cygwin setup utility. You must manually specify that you want 2.6.8. 3. Subversion 1.7: If not, you get errors updating sources due to incompatible authentication with svn.webkit.org. I also noticed that Cygwin tried to update to GNU Make 4.0; I left it at 3.82.90 since our Mac builders use 3.81 and I wanted to avoid yet another possible difference. I experimented with using the 64-bit Cygwin installation, but found that their build of bison failed to process our CSSGrammar.y file (exiting with error 141 without doing anything). The 32-bit build of bison does not share this problem. While there is a significant benefit to sharing the various build scripts and setup routines with our UNIX-flavored ports, I’m growing increasingly concerned that relying on Cygwin to provide similar benefits on Windows may become more difficult. I would love to move our Python requirement to 2.7 to be more consistent with our Mac builders, but have not found a suitable workaround. Are any other WebKit people aware of this problem or solutions for Cygwin? Thanks, -Brent
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
