Skip to content

Latest commit

 

History

History
59 lines (39 loc) · 3.09 KB

README-V8.md

File metadata and controls

59 lines (39 loc) · 3.09 KB

V8 JavaScript engine

PlaygroundJS uses the v8 JavaScript engine to execute the JavaScript parts of the gamemode. This document describes which revision we're using, and how to build the libraries required for running the plugin.

Current revision

PlaygroundJS tracks the master branch of v8, and is currently build against the following revision:

8bff3324c9702691f252b91b0511ebdb03ed6e45
"Version 8.5.74"
Saturday, May 30th, 2020

This is reflected in the //src/v8 folder, which will load the given revision of the v8 JavaScript engine as a git submodule.

Updating the version of v8 we use involves changing the submodule to refer to the new revision, making sure everything builds on both Windows and Linux and checking in the new binaries, v8.dll and libv8.so, in //bin.

Building v8

If you want to change the plugin itself, or update the version of v8 that's being used, make sure that you've got depot_tools installed and available in your PATH.

First time compilation (Linux only)

If this is the first time you're building v8 on Linux, run the following commands to initialize your environment.

$ git submodule update --init --recursive
$ sudo yum install glibc-static

Depending on the distribution, a more modern compiler may be necessary too.

Common steps

The following preparatory steps have to be executed on all platforms. They check out v8 including all the dependencies specific to the platform.

$ cd src/v8
$ git pull --rebase
$ git checkout 8.5.74
$ gclient sync

Building on Windows

On Windows, run the following command to create an MSVC-compatible binary:

$ set DEPOT_TOOLS_WIN_TOOLCHAIN=0
$ set GYP_MSVS_VERSION=2019
$ set GYP_CHROMIUM_NO_ACTION=0
$ gn gen --ide=vs2019 --args="target_cpu=\"x86\" is_component_build=true is_debug=false v8_use_external_startup_data=false is_clang=false use_custom_libcxx=false" out.gn\x86.release
$ ninja -C out.gn/x86.release v8 v8_libplatform

Browse to src\v8\out.gn\x86.release where you will find v8.dll, v8_libbase.dll and v8_libplatform.dll that have to be copied to the //bin directory.

Further, Boost will have to be built. After running the bootstrap, the following command is of use:

$ b2.exe architecture=x86 --with-filesystem --with-system --with-regex --with-date_time --with-thread

Or, on Linux:

$ ./b2 architecture=x86 address-model=32 link=static runtime-link=static --with-filesystem --with-system --with-regex --with-date_time --with-thread

Building on Linux

On Linux, the following commands should be used to compile v8 completely from the command line.

$ gn gen --args='target_cpu="x86" is_component_build=true is_debug=false v8_use_external_startup_data=false is_clang=false use_custom_libcxx=false' out.gn/x86.release
$ ninja -C out.gn/x86.release v8 v8_libplatform

The Makefile will automatically copy the required files to the appropriate directories.