Building on Windows - avoiding "goma" dependency, or how to get goma?

70 views
Skip to first unread message

Neil Moore

unread,
Jun 14, 2016, 4:26:14 AM6/14/16
to v8-users
I have followed steps from here to build on Windows. I used these steps:

# in windows command line
# have already installed gclient
fetch v8
cd v8
set DEPOT_TOOLS_WIN_TOOLCHAIN=0
set GYP_MSVS_VERSION=2013
set GYP_GENERATORS=ninja,ninja-msvs
gclient sync
python gypfiles\gyp_v8

but last line fails with

gyp: Call to '/bin/echo -n ${HOME}/goma' returned exit status 1 while in C:\Users\labuser\tmp\v8next\v8\gypfiles\all.gyp.

It doesn't generate any Visual Studio 2013 project.

I've got a few questions:

- How do I remove this dependency on goma? It seems to be something for Google staff? Presumably this shouldn't be happening to me. It seemed to only start to block me after I had been working with v8 for a couple of days, before I couldn't build but the error was different.
- Does anybody see anything missing from my Windows build steps?
- I really don't want to use Ninja, I'd rather use Visual Studio only. Is that a supported option?

- Is Visual studio 2015 supported?
Thanks and let me know if I've missed out any relevant information.

Neil

Michael Achenbach

unread,
Jun 14, 2016, 8:55:19 AM6/14/16
to v8-users
Note that the ninja build instructions are from the linux section.

Getting rid of goma:
set GYP_DEFINES="use_goma=0"

But rather refer to the windows instructions, ninja should be supported but isn't well tested:

MSVS 2015 is not yet supported. Tracking bug: crbug.com/603131

Cheers
Michael

Michael Achenbach

unread,
Jun 14, 2016, 8:57:31 AM6/14/16
to v8-users

But rather refer to the windows instructions, ninja should be supported but isn't well tested:


Disregard this, I see now that the instructions also describe ninja. That might have changed recently. 

Michael Achenbach

unread,
Jun 14, 2016, 8:59:05 AM6/14/16
to v8-users
Reply all
Reply to author
Forward
0 new messages