Installing the Developer Tools
Mac OS X
Get Xcode from https://developer.apple.com/downloads. Xcode 4.6 or later is required to build.
Install the Xcode Command Line Tools (located under Xcode Preferences > Downloads)
Note: Before you can use the command line tools, you must either run
sudo xcode-select -switch /Applications/Xcode.appor set the environment variable DEVELOPER_DIR to
/Applications/Xcode.app/Contents/Developer. See the
xcode-selectman page for more details.
Install Java for Mac OS X Developer Package
Download and install the latest OS-appropriate “Java for Mac OS X Developer Package” from https://developer.apple.com/downloads.
You can build with either Visual Studio 2010 or Visual Studio 2010 express. (Newer versions currently unsupported)
If you are building from Vista, install Service Pack 1 Update for Windows Vista.
Use the default options for these installations.
Cygwin is a collection of utilities for Windows that includes not only a Subversion client, but also additional tools that are required to build the WebKit source. We have made a downloader available that automatically collects all of the required packages.
Extract the content of the archive to some folder and start
cygwin-downloader.exefrom that folder. This will download all the Cygwin packages you need.
When all the packages have finished downloading, the Cygwin installer will launch. Choose Install from Local Directory, then click Next until the install is complete. If you are running Vista, the installer won't be able to launch automatically, so you will have to manually launch Cygwin's Setup.exe.
Note: If you are behind a proxy you need to set the
http_proxyenvironment variable to the URL of the proxy. This would likely match this pattern:
http[s]://[username[:password]@]somehost.com[:port]. Where the square brackets () are not part of the url but enclose url elements that are optional indicating that those elements might be missing in your case together with their enclosed delimiter such as @ and :.
Note: Vista may warn you that Cygwin did not install correctly. Ignore this warning and tell Vista that the install was successful.
Warning: If you are running Vista or Windows 7, Cygwin may have trouble with implementing
fork(the POSIX function frequently used to start child processes, needed by many of the WebKit build tools). In order to enable
cygwin1.dllto implement fork successfully it is better if no DLL loaded in the parent process is relocated at runtime. One way to achive this is to rebase all cygwin dlls except
cygwin1.dllto base addresses that cause them to not overlap in memory.
In order to rebase all cygwin dlls a
rebaseallscript is provided in the cygwin installation's
C:\cygwin\bin). This script must be run from
ash.exe(found in the same directory) while no other cygwin application is running.
ash.exehas very limited command line editing features so cutting and pasting to the commandline is recommended.
PATHenvironment variable may not contain the
/bindirectory by default thus the script should be launched as
rebaseallis complaining about failure to write to a Windows Temp directory (i.e.
/cygdrive/c/Users/you/AppData/Local/Temp), fix the permissions on that folder (i.e.
/bin/chown you /cygdrive/c/Users/you/AppData/Local/Temp) or change the TMP environment variable to point to a directory with the appropriate permission flags (i.e.:
Note: The rebase process may need to be repeated to include any new libraries added later to cygwin by listing these libraries by full cygwin path in a file and passing the file to
-T fileNamecommandline argument. The dlls under
LayoutTests/http/confare a relevant use case.
Remove the following lines from
/home/[username]/.bashrc(if present):unset TMPunset TEMPThose lines would prevent picking up the Windows TMP and TEMP environment variables.
If you are behind a proxy you need to do the following to allow cygwin svn to get through the proxy (similar steps are available for your Windows svn):
- In bash (Cygwin) run:
svn help. This will create in your cygwin home directory the file .subversion/servers.
- Edit the file mentioned above and follow the instructions in the file to set up your proxy settings.
- In bash (Cygwin) run:
Install QuickTime SDK and QuickTime
Download QuickTime SDK for Windows from http://developer.apple.com/quicktime/download/ and install it to the default location (\Program Files\QuickTime SDK). This is needed for media support.
You'll also want quicktime itself. You don't need it to build but without it media fallbacks won't work.
Install DirectX SDK
Download the June 2010 DirectX SDK This is needed for accelerated compositing.
Install php, we use the following steps (you need this to run http layout tests):
- cd /usr/local/bin
- wget http://apt-cyg.googlecode.com/svn/trunk/apt-cyg
- chmod a+x apt-cyg
- Change line 341 of the apt-cyg script to "wget -nc $mirror/../$install"
- apt-cyg -m ftp://sourceware.org/pub/cygwinports/x86 install php
Optional: Install the 32-bit version of Debugging Tools for Windows
Debugging Tools for Windows includes many useful debugging tools such as WinDbg and NTSD. Some of WebKit’s tests and scripts use these tools. Follow the instructions for installing the 32-bit version of Debugging Tools for Windows.
Optional: Hotfix for 64-bit Windows to disable the user-mode callback filter for exceptions
Without the 976038 hotfix, exceptions may be thrown in callback routines that do not cause a crash but leave the application in an inconsistent state that might cause a crash later. You will need to click on "View and request hotfix downloads" and fill out the form. A link to download the hotfix and a password will be emailed to you.
GTKFollow the instructions on the BuildingGTK wiki page.
QTFollow the instructions on the QtWebKit wiki page.
EFLFollow the instructions on the EFLWebKit wiki page.
Once you have installed your developer tools, the next step is getting the code.