See also https://bugs.chromium.org/p/v8/issues/detail?id=4847
The CL that changes this will land in a few days:
https://codereview.chromium.org/1811283002/
--
Michael Achenbach | Software Engineer, Tools & Infrastructure, V8 | Google
Germany GmbH | Erika-Mann-Str. 33, 80636 München
Register
I'll land this now.
On Fri, Mar 18, 2016 at 11:43 AM, Michael Achenbach
wrote:
> See also https://bugs.chromium.org/p/v8/issues/detail?id=4847
>
> The CL that changes this will land in a few days:
> https://codereview.chromium.org/1811283002/
>
> --
>
> Michael Achenbach | Software Engineer, To
This moved to gypfiles as part of the GN transition. The documentation is
out of date and nobody tested this properly afterwards.
Could you provide more details, why gypfiles/gyp_v8 doesn't work?
On Sunday, May 15, 2016 at 4:06:06 AM UTC+2, Garrett Hoofman wrote:
>
> gyp_v8 is missing? Or the i
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:
https://github.com/v8/v8/wiki/Building%20with%20Gyp#visual-studio
MSVS 2015 is not
>
>
> But rather refer to the windows instructions, ninja should be supported
> but isn't well tested:
> https://github.com/v8/v8/wiki/Building%20with%20Gyp#visual-studio
>
>>
>>
Disregard this, I see now that the instructions also describe ninja. That
might have changed recently.
--
--
v8-u
On Tuesday, June 14, 2016 at 2:57:31 PM UTC+2, Michael Achenbach wrote:
>
>
>> But rather refer to the windows instructions, ninja should be supported
>> but isn't well tested:
>> https://github.com/v8/v8/wiki/Building%20with%20Gyp#visual-studio
>>
>>>
>>>
> Disregard this, I see now that the in
Note that MSVS 2015 is not officially supported by v8 yet (is might work
but is not continuously tested).
More docu about the windows build procedure is here (but I think this
thread already covers it all):
https://github.com/v8/v8/wiki/Building%20with%20Gyp#prerequisites
On Monday, July 11, 20
Please see https://github.com/v8/v8/wiki/Building-with-Gyp#prerequisites
You need to
set DEPOT_TOOLS_WIN_TOOLCHAIN=0
if you are not a googler.
On Monday, July 25, 2016 at 4:53:21 PM UTC+2, spaesani...@gmail.com wrote:
>
> I just tried again through windows console and I get passed (or prior)
If the environment variable DEPOT_TOOLS_WIN_TOOLCHAIN had been set to 0,
python wouldn't get passed this condition:
https://cs.chromium.org/chromium/src/v8/gypfiles/vs_toolchain.py?q=vs_tool&sq=package:chromium&l=42
as depot_tools_win_toolchain is set above to:
depot_tools_win_toolchain =
bool(i
>
> To be clear the issue is the* current_hashes [] *
> It's empty.
> It's set in get_toolchain_if_necesssary.py around line 480
>
> current_hashes = CalculateToolchainHashes(target_dir, True)
>
> I'm not familiar with google builds and have no idea what it's looking
> for.
>
I can only repe
Please provide the exact commands you used - also v8 revision and gn args.
On Friday, September 9, 2016 at 7:02:46 PM UTC+2, Matt Peterson wrote:
>
> So I've been trying to build v8 for android using GN, and every time I
> try, with multiple versions, I get the same error. It seems like
> native
I actually think this is a bug in our work flow. I
filed http://crbug.com/648583
You can also pass -p to v8gen.py to let it perform an additional gn run
over the extra cmd line parameters automatically.
On Tuesday, September 20, 2016 at 9:16:56 AM UTC+2, Jochen Eisinger wrote:
>
> v8gen creates
That'd be with
set GYP_GENERATORS=msvs
But I'm afraid we dropped official support for this a while back.
Why not build with ninja? E.g. gyp_generator like you specified and then
build with:
ninja -C out\Release
on x64 platforms might require:
ninja -C out\Release_x64
On Wednesday, September 21
This is now fixed by http://crbug.com/648583
Now gn should automatically rebuild after using v8gen. No need to pass -p
(unless you want early checking) or to call gn manually.
On Tuesday, September 20, 2016 at 3:42:28 PM UTC+2, Andre Cunha wrote:
>
> I tried the following sequence of commands:
>
You need this in your args.gn:
is_clang=false
use_sysroot=false
On Wednesday, September 28, 2016 at 2:15:47 AM UTC+2, Ivan P. wrote:
>
> Amendment: used ninja -v -C out.gn/test1
> So I can see all commands executed in console output, and I can see it
> uses clang++.
>
> среда, 28 сентября 2016 г
Hi!
We track this feature here: http://crbug.com/v8/5435
See also this previous discussion for a way around in the mean time:
https://groups.google.com/forum/#!topic/v8-users/ooO1Bf8sZ_g
Furthermore, GYP is still supported. We will first remove GYP support in V8
when GN satisfies all requiremen
Please refer to the authors of the gn --ide=vs extension. I don't know what
this is supposed to be doing.
V8 officially only supports building with ninja. E.g.
gn gen v5.4/x64.release
ninja -C v5.4/x64.release d8
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/gr
I don't know if the --ide option can be used for building V8. We don't
officially support it. The stackoverflow link you provided contains also
the answer we officially support:
http://stackoverflow.com/a/39550343
Could you try building with ninja and see if it works for you?
Of course, if you
Is it different with ToT? Please see http://crbug.com/v8/6461 which
introduced a recent fix.
On Monday, June 26, 2017 at 9:45:27 AM UTC+2, Hans Maier wrote:
>
> I just tried it with 5.9.211.38 under Windows with VS2015 and the
> following args:
> is_debug = false
> target_cpu = "x64"
> v8_static
Officially we currently support version 2015 in V8 only. 2013 won't work
anymore because of unsupported C++ features (I think).
Chromium seems to start supporting 2017 as well, but in V8 we have a few
legacy scripts that are not up-to-date with Chromium.
E.g. v8\gypfiles\vs_toolchain.py is an o
Thanks Bruce!
I'll track this now as https://crbug.com/v8/6584. No ETA yet when I get to
it though.
On Monday, July 10, 2017 at 7:20:01 PM UTC+2, Bruce Dawson wrote:
>
> Resending now that I've joined the group...
>
> > Officially we currently support version 2015 in V8 only. 2013 won't
> work
Note: The source of truth still remains svn for a while.
The svn revision numbers can be found in a stamp on the bottom of the git
commits. E.g. here:
https://chromium.googlesource.com/v8/v8/+/86da2033a81f5e51ea57028027be6eac208b9dfb
it is
git-svn-id: https://v8.googlecode.com/svn/trunk@24637
Hi v8 developers, contributers and users!
V8 will migrate to git on November the 12th between 6 and 7 p.m. CET (9 and
10 a.m. PST).
If you haven't done so already, please switch to the new git workflow as
documented here:
https://code.google.com/p/v8-wiki/wiki/UsingGit#Git_repository
If you are
The v8 git migration is starting now.
On Fri, Nov 7, 2014 at 2:37 PM, Michael Achenbach
wrote:
> Hi v8 developers, contributers and users!
>
> V8 will migrate to git on November the 12th between 6 and 7 p.m. CET (9
> and 10 a.m. PST).
>
> If you haven't done so already, please switch to the new
Hi v8 developers, contributors and users!
V8 migrated successfully to git!
If you haven't done so already, please switch to the new git workflow as
documented here:
https://code.google.com/p/v8-wiki/wiki/UsingGit#Git_repository
If you are a committer, please prepare your .netrc file as documente
Hi V8 developers and contributors!
We have a CQ now. For committing your patches, please prefer the CQ check
box on codereview over 'git cl land'. You can also use the revert button
there. See also https://code.google.com/p/v8-wiki/wiki/UsingGit#Committing
Note that the CQ has not the full covera
Please don't merge patches into 3.31. This branch is orphaned as we decided
to bump the milestone number.
Current stable: 3.30
Current beta: 4.1
--
Michael Achenbach
V8 Test Engineer
Google Germany GmbH
Dienerstr. 12
80331 München
*--
Registergericht u
27 matches
Mail list logo
