The WebKitRequirements repository uses GitHub releases to host a distribution which are then downloaded by scripts contained in the WebKit repository. By default the latest release will be downloaded when doing a WebKit build. Each release corresponds to a tag within the git repository.
Tags are done based on the date of creation of the distribution. This is done because the third party requirements change sporadically and semantic versioning does not fit with the distribution. This provides a clear timeline on when the requirements changed.
To create the tag have the commit that is being released checked out locally. From there run the following commands where YYYY.MM.DD corresponds to the year month and day the tag is created.
git tag -a vYYYY.MM.DD -m "vYYYY.MM.DD"
git push origin vYYYY.MM.DD
Once the tag is pushed a release can be created within GitHub.
The WebKitRequirements repository uses Drone to build the release when a tag is pushed. It will create a GitHub release associated with the tag and create the distribution for 32 and 64-bit WinCairo builds.
The repository contains a number of scripts to create a distribution. These are used to build locally consistently.
All the scripts take a triplet value which specifies the toolchain. For
building WebKitRequirements two toolchain files were created because there are
some libraries that need to be built statically even when a dynamic build is
wanted.
The Install-Requirements.ps1 script is a wrapper around vcpkg which will
invoke vcpkg install with a list of requirements. The requirements are
defined in a .json file which is nothing more than a list of port names.
The Release-Requirements.ps1 script creates a zip file containing the
dependencies. If a different filename is required then set the -Output flag
accordingly.
& Install-Requirements.ps1 -triplet x64-windows-webkit
& Release-Requirements.ps1 -triplet x64-windows-webkit