The bindings are tested to work with several recent v8 builds matching the Chrome builds 54 - 60 (see the .travis.yml file for specific versions). For example, Chrome 59 (dev branch) uses v8 184.108.40.206 when this was written.
Note that v8 releases match the Chrome release timeline: Chrome 48 corresponds to v8 4.8.*, Chrome 49 matches v8 4.9.*. You can see the table of current chrome and the associated v8 releases at:
Using a pre-compiled v8
v8 is very slow to compile, it's a large project. If you want to go that route, there are building instructions below.
Fortunately, there's a project that pre-builds v8 for various platforms. It's packaged as a ruby gem called libv8.
# Find the appropriate gem version for your OS, # visit: https://rubygems.org/gems/libv8/versions # Download the gem # MacOS Sierra is darwin-16, for v8 6.3.292.48.1 it looks like: curl https://rubygems.org/downloads/libv8-6.3.292.48.1-x86_64-darwin-16.gem > libv8.gem # Extract the gem (it's a tarball) tar -xf libv8.gem # Extract the `data.tar.gz` within cd libv8-6.3.292.48.1-x86_64-darwin-16 tar -xzf data.tar.gz # Symlink the compiled libraries and includes ln -s $(pwd)/data/vendor/v8/include $GOPATH/src/github.com/augustoroman/v8/include ln -s $(pwd)/data/vendor/v8/out/x64.release $GOPATH/src/github.com/augustoroman/v8/libv8 # Run the tests to make sure everything works cd $GOPATH/src/github.com/augustoroman/v8 go test
Using docker (linux only)
For linux builds, you can use pre-built libraries or build your own.
To use a pre-built library, select the desired v8 version from https://hub.docker.com/r/augustoroman/v8-lib/tags/ and then run:
# Select the v8 version to use: export V8_VERSION=6.7.77 docker pull augustoroman/v8-lib:$V8_VERSION # Download the image, updating if necessary. docker rm v8 ||: # Cleanup from before if necessary. docker run --name v8 augustoroman/v8-lib:$V8_VERSION # Run the image to provide access to the files. docker cp v8:/v8/include include/ # Copy the include files. docker cp v8:/v8/lib libv8/ # Copy the library fiels.
Build your own via docker
This takes a lot longer, but is still easy:
export V8_VERSION=6.7.77 docker build --build-arg V8_VERSION=$V8_VERSION --tag augustoroman/v8-lib:$V8_VERSION docker-v8-lib/
and then extract the files as above:
docker rm v8 ||: # Cleanup from before if necessary. docker run --name v8 augustoroman/v8-lib:$V8_VERSION # Run the image to provide access to the files. docker cp v8:/v8/include include/ # Copy the include files. docker cp v8:/v8/lib libv8/ # Copy the library fiels.
You need to build v8 statically and place it in a location cgo knows about. This requires special tooling and a build directory. Using the official instructions as a guide, the general steps of this process are:
go getthe binding library (this library)
- Create a v8 build directory
- Install depot tools
- Configure environment
- Download v8
- Build v8
- Copy or symlink files to the go library path
- Build the bindings
go get github.com/augustoroman/v8 export V8_GO=$GOPATH/src/github.com/augustoroman/v8 export V8_BUILD=$V8_GO/v8/build #or wherever you like mkdir -p $V8_BUILD cd $V8_BUILD git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git export PATH=$PATH:$V8_BUILD/depot_tools fetch v8 #pull down v8 (this will take some time) cd v8 git checkout 6.7.77 gclient sync
./build/install-build-deps.sh #only needed once gn gen out.gn/golib --args="strip_debug_info=true v8_use_external_startup_data=false v8_enable_i18n_support=false v8_enable_gdbjit=false v8_static_library=true symbol_level=0 v8_experimental_extra_library_files= v8_extra_library_files=" ninja -C out.gn/golib # go get some coffee
gn gen out.gn/golib --args="is_official_build=true strip_debug_info=true v8_use_external_startup_data=false v8_enable_i18n_support=false v8_enable_gdbjit=false v8_static_library=true symbol_level=0 v8_experimental_extra_library_files= v8_extra_library_files=" ninja -C out.gn/golib # go get some coffee
Now you can create symlinks so that cgo can associate the v8 binaries with the go library.
cd $V8_GO ./symlink.sh $V8_BUILD/v8
You should be done! Try running
Also relevant is the v8 API release changes doc:
This work is based off of several existing libraries: