[v8-users] How to contribute a patch to V8

[Ivan Pizhenko]

Hi,
I want to contribute a small fix (like couple lines of code) to the V8 
build scripts for Windows. How can I do it? (Note that I am not a Google 
employee or otherwise affiliated Chromium or V8 developer.)
WBW, Ivan 

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/eccd4374-2fa5-4883-9b34-65c9a9961b34n%40googlegroups.com.

RE: [v8-users] Re: Building v8 shared library on windows

[Ivan Pizhenko]

Still can’t get it working. Note - I am trying to compile v8 7.8.279.23

For example:

[105/1253] 
L:/depot_tools/bootstrap-3_8_0b1_chromium_1_bin/python/bin/python.exe 
../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x64 False 
link.exe /nologo /OUT:./bytecode_builtins_list_generator.exe 
/PDB:./bytecode_builtins_list_generator.exe.pdb 
@./bytecode_builtins_list_generator.exe.rsp
FAILED: bytecode_builtins_list_generator.exe 
bytecode_builtins_list_generator.exe.pdb
L:/depot_tools/bootstrap-3_8_0b1_chromium_1_bin/python/bin/python.exe 
../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x64 False 
link.exe /nologo /OUT:./bytecode_builtins_list_generator.exe 
/PDB:./bytecode_builtins_list_generator.exe.pdb 
@./bytecode_builtins_list_generator.exe.rsp
generate-bytecodes-builtins-list.obj : error LNK2019: unresolved external 
symbol "public: static void __cdecl 
v8::internal::Internals::CheckInitializedImpl(class v8::Isolate *)" 
(?CheckInitializedImpl@Internals@internal@v8@@SAXPEAVIsolate@3@@Z) referenced 
in function "public: static void __cdecl 
v8::internal::Internals::CheckInitialized(class v8::Isolate *)" 
(?CheckInitialized@Internals@internal@v8@@SAXPEAVIsolate@3@@Z)

and many more of that.

Seems like such unresolved functions are located in the source code files that 
were not compiled.

For example:

bytecode-operands.obj : error LNK2001: unresolved external symbol "private: 
static void __cdecl v8::Int32::CheckCast(class v8::Value *)" 
(?CheckCast@Int32@v8@@CAXPEAVValue@2@@Z)

This one is located in the v8/src/api/api.cc

But when I am checking my v8\out.gn.windows\x64.debug\.ninja.log api.obj is not 
mentioned there.

Is these some missing dependency in the build files?

From: Ivan Pizhenko<mailto:ivan.pizhe...@genesys.com>
Sent: Friday, December 20, 2019 20:29
To: v8-users@googlegroups.com<mailto:v8-users@googlegroups.com>
Subject: RE: [v8-users] Re: Building v8 shared library on windows

Oh, that’s great. Thank you. I will try to apply similar patch locally to the 
7.8.279.23, since I am allowed to use only “stable” versions of V8.
- Ivan


From: 'Bill Ticehurst' via v8-users<mailto:v8-users@googlegroups.com>
Sent: Friday, December 20, 2019 20:02
To: v8-users<mailto:v8-users@googlegroups.com>
Subject: [v8-users] Re: Building v8 shared library on windows

FWIW: I played around with the last night for a couple hours and got a release 
build working using a "component build" and MSVC. It was mostly moving some 
inline functions and adding some V8_EXPORT_PRIVATE statements (which 
effectively add the "__declspec(dllexport)" statements to expose functions 
across DLLs with MSVC). You can see the changes over the current V8 v8.0 branch 
at https://github.com/v8/v8/compare/8.0-lkgr...billti:v8.0-msvc-fixes?expand=1

This is very rough code, hacking away at one build break at a time until it 
worked. I'll need to clean it up with a consistent approach before it would be 
ready for a CL. It also only works for the product binaries & D8 so far (i.e. 
build with "ninja -C out.gn\x64.release d8"), so I need to fix up the failures 
when building the test code (which means figuring out some of the subtlety in 
https://github.com/v8/v8/blob/master/src/base/export-template.h ).

Bottom line: It seems fixable without major changes, and should be very low 
risk (as the V8_EXPORT_* macros effectively compile to nothing in static builds 
- which is what Chromium and Node.js use for release).

 - Bill

On Wednesday, December 18, 2019 at 10:06:42 AM UTC-8, Bill Ticehurst wrote:
I'm not clear on what is needed to fix this. The bug has been open quite a 
while (see https://bugs.chromium.org/p/v8/issues/detail?id=8791).

On Tuesday, December 17, 2019 at 12:44:14 PM UTC-8, Ivan Pizhenko wrote:
Hi Bill, so what needs to be fixed to get DLL build (i.e. 
is_component_build=true) built successfully with MSVC compiler?
I've recently run into the same linking issue with DLL build compiled using 
clang. And to say truth, it's weird that DLL build works only with clang.
p.s. I cannot use prebuilt binaries from nuget and cannot use clang to build my 
app. Need to use strictly MSVC 2017.

- Ivan

On Tuesday, December 17, 2019 at 6:36:12 PM UTC+2, Bill Ticehurst wrote:
To be clear, NuGet is a Microsoft run package manager, but "Microsoft" doesn't 
offer any pre-built V8 binaries. A user account named "pmed" created/uploaded 
that package, not a Microsoft account.

If you are building V8 in a default manner with Clang as it appears, then you 
can't link it with a project you're building with the MSVC compiler. Those are 
two different compilers and C++ doesn't have a cross compiler stable ABI 
(especially if using "custom_libcxx", which means they are also using a 
different standard C++ library - V8 the Clang provided "libc++", and MSVC will 
use it's own).

If you 

RE: [v8-users] Re: Building v8 shared library on windows

[Ivan Pizhenko]

Oh, that’s great. Thank you. I will try to apply similar patch locally to the 
7.8.279.23, since I am allowed to use only “stable” versions of V8.
- Ivan


From: 'Bill Ticehurst' via v8-users<mailto:v8-users@googlegroups.com>
Sent: Friday, December 20, 2019 20:02
To: v8-users<mailto:v8-users@googlegroups.com>
Subject: [v8-users] Re: Building v8 shared library on windows

FWIW: I played around with the last night for a couple hours and got a release 
build working using a "component build" and MSVC. It was mostly moving some 
inline functions and adding some V8_EXPORT_PRIVATE statements (which 
effectively add the "__declspec(dllexport)" statements to expose functions 
across DLLs with MSVC). You can see the changes over the current V8 v8.0 branch 
at 
https://github.com/v8/v8/compare/8.0-lkgr...billti:v8.0-msvc-fixes?expand=1<https://github.com/v8/v8/compare/8.0-lkgr...billti:v8.0-msvc-fixes?expand=1>

This is very rough code, hacking away at one build break at a time until it 
worked. I'll need to clean it up with a consistent approach before it would be 
ready for a CL. It also only works for the product binaries & D8 so far (i.e. 
build with "ninja -C out.gn\x64.release d8"), so I need to fix up the failures 
when building the test code (which means figuring out some of the subtlety in 
https://github.com/v8/v8/blob/master/src/base/export-template.h<https://github.com/v8/v8/blob/master/src/base/export-template.h>
 ).

Bottom line: It seems fixable without major changes, and should be very low 
risk (as the V8_EXPORT_* macros effectively compile to nothing in static builds 
- which is what Chromium and Node.js use for release).

 - Bill

On Wednesday, December 18, 2019 at 10:06:42 AM UTC-8, Bill Ticehurst wrote:
I'm not clear on what is needed to fix this. The bug has been open quite a 
while (see 
https://bugs.chromium.org/p/v8/issues/detail?id=8791<https://bugs.chromium.org/p/v8/issues/detail?id=8791>).

On Tuesday, December 17, 2019 at 12:44:14 PM UTC-8, Ivan Pizhenko wrote:
Hi Bill, so what needs to be fixed to get DLL build (i.e. 
is_component_build=true) built successfully with MSVC compiler?
I've recently run into the same linking issue with DLL build compiled using 
clang. And to say truth, it's weird that DLL build works only with clang.
p.s. I cannot use prebuilt binaries from nuget and cannot use clang to build my 
app. Need to use strictly MSVC 2017.

- Ivan

On Tuesday, December 17, 2019 at 6:36:12 PM UTC+2, Bill Ticehurst wrote:
To be clear, NuGet is a Microsoft run package manager, but "Microsoft" doesn't 
offer any pre-built V8 binaries. A user account named "pmed" created/uploaded 
that package, not a Microsoft account.

If you are building V8 in a default manner with Clang as it appears, then you 
can't link it with a project you're building with the MSVC compiler. Those are 
two different compilers and C++ doesn't have a cross compiler stable ABI 
(especially if using "custom_libcxx", which means they are also using a 
different standard C++ library - V8 the Clang provided "libc++", and MSVC will 
use it's own).

If you build V8 with Clang, you'll should build your project with Clang too 
(ideally using the same build toolchain - i.e. by updating the BUILD.gn file to 
include a target for your project - the doc at 
https://v8.dev/docs/embed<https://v8.dev/docs/embed> details the Process and 
Shell sample apps which build via BUILD.gn and you can follow as an example). 
If you do decide to build V8 with MSVC, then as mentioned previously, 
"component build" isn't working currently, and you'll need to static link 
everything together ("is_component_build = false"), resulting in a large 
binary, rather than several V8 DLLs and a small application exe).

 - Bill

On Tuesday, December 17, 2019 at 4:31:52 AM UTC-8, Stefan Wörthmüller wrote:
Note that Microsoft also offers prebuild verrions of v8 via the package manager 
or direct to download.
I.e. 
https://www.nuget.org/packages/v8-v140-x64/<https://www.nuget.org/packages/v8-v140-x64/>
 click on "Download" at the right and rename the archive to zip. Works well for 
me.

--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users<http://groups.google.com/group/v8-users>
---
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
v8-users+unsubscr...@googlegroups.com<mailto:v8-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/a0a7c08b-7ff7-40cf-9104-021a97912018%40googlegroups.com<https://groups.google.com/d/msgid/v8-users/a0a7c08b-7ff7-40cf-9104-021a97912018%40googlegroups.com?utm_medium=email_source=footer>.

-- 
-- 
v8-users mailing list
v8-u

RE: [v8-users] Re: Building v8 shared library on windows

[Ivan Pizhenko]

Yes, that’s true. But fortunately, I don’t use all that stuff that has STL 
classes in the interface, except libplatform, so works for me, and may work for 
someone else.


From: 'Bill Ticehurst' via v8-users<mailto:v8-users@googlegroups.com>
Sent: Thursday, December 19, 2019 20:43
To: v8-users<mailto:v8-users@googlegroups.com>
Subject: Re: [v8-users] Re: Building v8 shared library on windows

Just the header file for the public V8 API 
(https://chromium.googlesource.com/v8/v8.git/+/refs/heads/master/include/v8.h#18<https://chromium.googlesource.com/v8/v8.git/+/refs/heads/master/include/v8.h#18>)
 includes , , , , and  from the 
C++ standard library. I'm unclear what they are all needed for, but I think 
it's safe to say mixing C++ standard libraries when building and consuming V8 
is always going to be high risk, unsupported, and if you do manage to get it 
working today - very fragile going forward.

 - Bill

On Thursday, December 19, 2019 at 7:55:52 AM UTC-8, ClearScript Developers 
wrote:
Unfortunately this issue transcends export naming. V8 seems to be embracing STL 
data types all over its API.

By sheer luck std::unique_ptr is likely to work across STL implementations (at 
least when used without a stateful deleter), but other data types aren't so 
lucky. V8 already has a bunch of APIs that pass or return std::shared_ptr, and 
that's pretty much guaranteed to fail.

On Wednesday, December 18, 2019 at 1:58:41 PM UTC-5, Ivan Pizhenko wrote:
That’s clear, the instruction under the link suggests to build V8 as static 
library, which we already know to be working. But the point was to build and 
use V8 as DLL. Meanwhile, I’ve found following workaround: add 2 new custom 
functions to the libplatform, the first one returns normal pointer extracted 
from return value of the NewDefaultPlatform() and second to delete v8::Platform 
object (this is to ensure we use both new and delete from libc++), and export 
these functions from DLL. This way I’ve gotten rid of dependency on the 
std::unique_ptr version coming from libc++. And based on this experience I’d 
generally suggest to V8 developers to keep all public V8 APIs w/o any STL stuff 
for the sake of better integration with different compilers, which with very 
high probability have different STL implementations than libc++.
- Ivan


From: 'Bill Ticehurst' via v8-users
Sent: Wednesday, December 18, 2019 20:22
To: v8-users
Subject: [v8-users] Re: Building v8 shared library on windows

I believe this is still mostly correct - (some filenames might be out of date, 
but should give you a general starting point). If you're already building V8 
successfully with MSVC, you should be able to skip down to the "Embedding V8 
into a custom application" part.

https://medium.com/angular-in-depth/how-to-build-v8-on-windows-and-not-go-mad-6347c69aacd4<https://medium.com/angular-in-depth/how-to-build-v8-on-windows-and-not-go-mad-6347c69aacd4>

Disclaimer: As should be obvious by now (and by the above post), this stuff is 
a moving target (e.g. changing compilers and build outputs over time), 
non-trivial, and not a first-class supported scenario. The "well trodden" and 
best supported path is to build your code via a new BUILD.gn target with Clang 
along with the rest of V8, that way you can ensure your compiler and build 
settings are all consistent, and the dependencies are largely managed for you. 
Good luck!

 - Bill

On Wednesday, December 18, 2019 at 3:09:50 AM UTC-8, Bad_At_Life wrote:
Ok Bill
Then I'll build it statically with "is_component_build = false". I don't really 
need them to be dynamic, I just need them to work.
What file extension should I look for? .lib?
Thank you
--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users<http://groups.google.com/group/v8-users>
---
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-u...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/554c96a8-82e1-4a6d-86c7-2a65d51c5797%40googlegroups.com<https://groups.google.com/d/msgid/v8-users/554c96a8-82e1-4a6d-86c7-2a65d51c5797%40googlegroups.com?utm_medium=email_source=footer>.

--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users<http://groups.google.com/group/v8-users>
---
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
v8-users+unsubscr...@googlegroups.com<mailto:v8-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/c64e6796-74f7-4bbd-9701-750632714cd7%40googlegroups.com<https://groups.google.com/d/msgid/v8-users/c64e6

RE: [v8-users] Re: Building v8 shared library on windows

[Ivan Pizhenko]

That’s clear, the instruction under the link suggests to build V8 as static 
library, which we already know to be working. But the point was to build and 
use V8 as DLL. Meanwhile, I’ve found following workaround: add 2 new custom 
functions to the libplatform, the first one returns normal pointer extracted 
from return value of the NewDefaultPlatform() and second to delete v8::Platform 
object (this is to ensure we use both new and delete from libc++), and export 
these functions from DLL. This way I’ve gotten rid of dependency on the 
std::unique_ptr version coming from libc++. And based on this experience I’d 
generally suggest to V8 developers to keep all public V8 APIs w/o any STL stuff 
for the sake of better integration with different compilers, which with very 
high probability have different STL implementations than libc++.
- Ivan


From: 'Bill Ticehurst' via v8-users
Sent: Wednesday, December 18, 2019 20:22
To: v8-users
Subject: [v8-users] Re: Building v8 shared library on windows

I believe this is still mostly correct - (some filenames might be out of date, 
but should give you a general starting point). If you're already building V8 
successfully with MSVC, you should be able to skip down to the "Embedding V8 
into a custom application" part.

https://medium.com/angular-in-depth/how-to-build-v8-on-windows-and-not-go-mad-6347c69aacd4

Disclaimer: As should be obvious by now (and by the above post), this stuff is 
a moving target (e.g. changing compilers and build outputs over time), 
non-trivial, and not a first-class supported scenario. The "well trodden" and 
best supported path is to build your code via a new BUILD.gn target with Clang 
along with the rest of V8, that way you can ensure your compiler and build 
settings are all consistent, and the dependencies are largely managed for you. 
Good luck!

 - Bill

On Wednesday, December 18, 2019 at 3:09:50 AM UTC-8, Bad_At_Life wrote:
Ok Bill
Then I'll build it statically with "is_component_build = false". I don't really 
need them to be dynamic, I just need them to work.
What file extension should I look for? .lib?
Thank you
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/554c96a8-82e1-4a6d-86c7-2a65d51c5797%40googlegroups.com.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/CY4PR10MB20235E157BF2E042427E9B33FF530%40CY4PR10MB2023.namprd10.prod.outlook.com.

[v8-users] Re: Building v8 shared library on windows

[Ivan Pizhenko]

Hi Bill, so what needs to be fixed to get DLL build (i.e. 
is_component_build=true) built successfully with MSVC compiler? 
I've recently run into the same linking issue with DLL build compiled using 
clang. And to say truth, it's weird that DLL build works only with clang. 
p.s. I cannot use prebuilt binaries from nuget and cannot use clang to 
build my app. Need to use strictly MSVC 2017.

- Ivan

On Tuesday, December 17, 2019 at 6:36:12 PM UTC+2, Bill Ticehurst wrote:
>
> To be clear, NuGet is a Microsoft run package manager, but "Microsoft" 
> doesn't offer any pre-built V8 binaries. A user account named "pmed" 
> created/uploaded that package, not a Microsoft account.
>
> If you are building V8 in a default manner with Clang as it appears, then 
> you can't link it with a project you're building with the MSVC compiler. 
> Those are two different compilers and C++ doesn't have a cross compiler 
> stable ABI (especially if using "custom_libcxx", which means they are also 
> using a different standard C++ library - V8 the Clang provided "libc++", 
> and MSVC will use it's own).
>
> If you build V8 with Clang, you'll should build your project with Clang 
> too (ideally using the same build toolchain - i.e. by updating the BUILD.gn 
> file to include a target for your project - the doc at 
> https://v8.dev/docs/embed details the Process and Shell sample apps which 
> build via BUILD.gn and you can follow as an example). If you do decide to 
> build V8 with MSVC, then as mentioned previously, "component build" isn't 
> working currently, and you'll need to static link everything together 
> ("is_component_build = false"), resulting in a large binary, rather than 
> several V8 DLLs and a small application exe).
>
>  - Bill
>
> On Tuesday, December 17, 2019 at 4:31:52 AM UTC-8, Stefan Wörthmüller 
> wrote:
>>
>> Note that Microsoft also offers prebuild verrions of v8 via the package 
>> manager or direct to download.
>> I.e. https://www.nuget.org/packages/v8-v140-x64/ click on "Download" at 
>> the right and rename the archive to zip. Works well for me.
>>
>>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/d436885c-434d-495d-8b64-282ad6f08c2b%40googlegroups.com.

Re: [v8-users] V8 build error on the CentOS 7

[Ivan Pizhenko]

Yes, I've found them in some .gni and .gn files and commented out. 
Regenerated build files and now build is running. I am using clang 7 from 
some previous stable version of V8.

On Monday, December 9, 2019 at 11:58:51 AM UTC+2, Jakob Kummerow wrote:
>
> On Fri, Dec 6, 2019 at 10:22 PM Ivan Pizhenko  > wrote:
>
>> Doesn't work. Seems like newer clang is required due to some options in 
>> the command line.
>>
>> *error: unknown warning option '-Wno-implicit-int-float-conversion'; did 
>> you mean '-Wno-float-overflow-conversion'? 
>> [-Werror,-Wunknown-warning-option]*
>> *error: unknown warning option '-Wno-xor-used-as-pow'; did you mean 
>> '-Wno-unused-macros'? [-Werror,-Wunknown-warning-option]*
>>
>
> Well, if it's just extra warnings, you can find out where they are defined 
> (I'd start by grepping for them in build/) and just remove them.
>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/c72465bf-0504-4cf5-a9d3-2b38f274e54c%40googlegroups.com.

Re: [v8-users] V8 build error on the CentOS 7

[Ivan Pizhenko]

w/o sysroot - gives errors, and I can't find how to get required packages, 
maybe GObject v2 is not on CentOS 7.

Got one  more idea - build clang 10.0.0 from sources on the centos7.

$ gn gen out.gn.linux/x64.debug
ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned 
non-zero exit code.
pkgresult = exec_script(pkg_config_script, args, "value")
^--
Current dir: 
/home/ivan/genesys/build/v8x/7.8.279.23_work/v8/out.gn.linux/x64.debug/
Command: python 
/home/ivan/genesys/build/v8x/7.8.279.23_work/v8/build/config/linux/pkg-config.py
 
glib-2.0 gmodule-2.0 gobject-2.0 gthread-2.0
Returned 1.
stderr:

Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
Package gmodule-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gmodule-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gmodule-2.0' found
Package gobject-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gobject-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gobject-2.0' found
Package gthread-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gthread-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gthread-2.0' found
Could not run pkg-config.

See //build/config/linux/BUILD.gn:89:3: whence it was called.
  pkg_config("glib") {
  ^---
See //build/config/compiler/BUILD.gn:235:18: which caused the file to be 
included.
configs += [ "//build/config/linux:compiler" ]
 ^--
 


On Friday, December 6, 2019 at 2:50:53 PM UTC+2, Jakob Kummerow wrote:
>
> You can try adding:
>
> is_clang = false
> use_sysroot = false
>
> to args.gn, but do note that this configuration is not officially 
> supported. If it works, you're in luck; if it doesn't, then CentOS 7 is 
> simply too old.
>
> (Side note: the recommended flow is to use "gn args " to edit the 
> args, instead of editing the file with any other editor and then invoking 
> "gn args" on it. But that's just a convenience thing; the end result should 
> be the same.)
>
>
> On Fri, Dec 6, 2019 at 1:12 PM Ivan P.  > wrote:
>
>> Hi, I'm trying to build on the CentOS 7 current stable version of V8 
>> 7.8.279.23 (i.e. version picked from the current stable Chrome version 
>> 78.0.3904.108) and getting error. 
>>
>> Here's what I've done:
>>
>> I've checked out sources and synchronized dependencies.
>>
>> I've prepared following gn config file
>>
>> # FILE: v8/out.gn.linux/x64.debug/gn.args
>> symbol_level=2
>> is_debug=true
>> is_component_build=true
>> target_cpu="x64"
>> v8_target_cpu="x64"
>> v8_postmortem_support=true
>> use_debug_fission=false
>> # END OF FILE
>>
>> And run 
>> gn args out.gn.linux/x64.debug
>>
>> After this I'm trying to run build process itself:
>> ninja -j3 -v -C out.gn.linux/x64.debug d8
>>
>> and I am getting following output with error (see in the bottom in *RED*
>> ):
>>
>> ninja: Entering directory `out.gn.linux/x64.debug'
>> [1/1302] ../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD 
>> -MF obj/torque_base/class-debug-reader-generator.o.d -DUSE_UDEV 
>> -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 
>> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
>> -D_GNU_SOURCE -DCR_CLANG_REVISION=\"369647-8288453f-2\" 
>> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DCOMPONENT_BUILD 
>> -D_LIBCPP_ABI_UNSTABLE -D_LIBCPP_ABI_VERSION=Cr -D_LIBCPP_ENABLE_NODISCARD 
>> -DCR_LIBCXX_REVISION=361348 
>> -DCR_SYSROOT_HASH=e7c53f04bd88d29d075bfd1f62b073aeb69cbe09 -D_DEBUG 
>> -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DENABLE_DISASSEMBLER 
>> -DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_GDB_JIT_INTERFACE 
>> -DENABLE_MINOR_MC -DOBJECT_PRINT -DVERIFY_HEAP -DV8_TRACE_MAPS 
>> -DV8_ENABLE_ALLOCATION_TIMEOUT -DV8_ENABLE_FORCE_SLOW_PATH 
>> -DV8_ENABLE_DOUBLE_CONST_STORE_CHECK -DV8_INTL_SUPPORT 
>> -DENABLE_HANDLE_ZAPPING -DV8_USE_SNAPSHOT 
>> -DV8_SNAPSHOT_NATIVE_CODE_COUNTERS -DV8_USE_EXTERNAL_STARTUP_DATA 
>> -DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
>> -DV8_CHECK_MICROTASKS_SCOPES_CONSISTENCY -DV8_EMBEDDED_BUILTINS 
>> -DV8_SHARED_RO_HEAP -DV8_WIN64_UNWINDING_INFO 
>> -DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_ENABLE_CHECKS 
>> -DV8_DEPRECATION_WARNINGS -DV8_IMMINENT_DEPRECATION_WARNINGS 
>> -DV8_TARGET_ARCH_X64 -DDEBUG -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
>> -DBUILDING_V8_SHARED -DV8_ENABLE_CHECKS -DV8_DEPRECATION_WARNINGS 
>> -DV8_IMMINENT_DEPRECATION_WARNINGS -DUSING_V8_BASE_SHARED -I../.. -Igen 
>> -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
>> -fstack-protector -funwind-tables -fPIC 
>> -B../../third_party/binutils/Linux_x64/Release/bin -pthread 
>> -fcolor-diagnostics -fmerge-all-constants 
>> 

Re: [v8-users] V8 build error on the CentOS 7

[Ivan Pizhenko]

Doesn't work. Seems like newer clang is required due to some options in the 
command line.

ninja: Entering directory `out.gn.linux/x64.debug'
[1/1302] ../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF 
obj/torque_base/class-debug-reader-generator.o.d -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-DCR_CLANG_REVISION=\"369647-8288453f-2\" -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DCOMPONENT_BUILD -D_LIBCPP_ABI_UNSTABLE 
-D_LIBCPP_ABI_VERSION=Cr -D_LIBCPP_ENABLE_NODISCARD 
-DCR_LIBCXX_REVISION=361348 
-DCR_SYSROOT_HASH=e7c53f04bd88d29d075bfd1f62b073aeb69cbe09 -D_DEBUG 
-DDYNAMIC_ANNOTATIONS_ENABLED=1 -DENABLE_DISASSEMBLER 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_GDB_JIT_INTERFACE 
-DENABLE_MINOR_MC -DOBJECT_PRINT -DVERIFY_HEAP -DV8_TRACE_MAPS 
-DV8_ENABLE_ALLOCATION_TIMEOUT -DV8_ENABLE_FORCE_SLOW_PATH 
-DV8_ENABLE_DOUBLE_CONST_STORE_CHECK -DV8_INTL_SUPPORT 
-DENABLE_HANDLE_ZAPPING -DV8_USE_SNAPSHOT 
-DV8_SNAPSHOT_NATIVE_CODE_COUNTERS -DV8_USE_EXTERNAL_STARTUP_DATA 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_CHECK_MICROTASKS_SCOPES_CONSISTENCY -DV8_EMBEDDED_BUILTINS 
-DV8_SHARED_RO_HEAP -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_ENABLE_CHECKS 
-DV8_DEPRECATION_WARNINGS -DV8_IMMINENT_DEPRECATION_WARNINGS 
-DV8_TARGET_ARCH_X64 -DDEBUG -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DBUILDING_V8_SHARED -DV8_ENABLE_CHECKS -DV8_DEPRECATION_WARNINGS 
-DV8_IMMINENT_DEPRECATION_WARNINGS -DUSING_V8_BASE_SHARED -I../.. -Igen 
-I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -funwind-tables -fPIC 
-B../../third_party/binutils/Linux_x64/Release/bin -pthread 
-fcolor-diagnostics -fmerge-all-constants 
-fcrash-diagnostics-dir=../../tools/clang/crashreports -Xclang -mllvm 
-Xclang -instcombine-lower-dbg-declare=0 -fcomplete-member-pointers -m64 
-march=x86-64 -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= 
-D__TIMESTAMP__= -Xclang -fdebug-compilation-dir -Xclang . 
-no-canonical-prefixes -Wall -Werror -Wextra -Wimplicit-fallthrough 
-Wthread-safety -Wextra-semi -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-c++11-narrowing 
-Wno-unneeded-internal-declaration -Wno-undefined-var-template 
-Wno-ignored-pragma-optimize -Wno-implicit-int-float-conversion 
-Wno-xor-used-as-pow -fno-omit-frame-pointer -g2 -ggnu-pubnames 
-fvisibility=hidden -Wheader-hygiene -Wstring-conversion 
-Wtautological-overlap-compare -Wmissing-field-initializers 
-Wunreachable-code -Wshorten-64-to-32 -O3 -fno-ident -fdata-sections 
-ffunction-sections -Wexit-time-destructors -Wno-undefined-bool-conversion 
-Wno-tautological-undefined-compare -std=c++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
--sysroot=../../build/linux/debian_sid_amd64-sysroot 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../src/torque/class-debug-reader-generator.cc -o 
obj/torque_base/class-debug-reader-generator.o
FAILED: obj/torque_base/class-debug-reader-generator.o 
../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF 
obj/torque_base/class-debug-reader-generator.o.d -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-DCR_CLANG_REVISION=\"369647-8288453f-2\" -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DCOMPONENT_BUILD -D_LIBCPP_ABI_UNSTABLE 
-D_LIBCPP_ABI_VERSION=Cr -D_LIBCPP_ENABLE_NODISCARD 
-DCR_LIBCXX_REVISION=361348 
-DCR_SYSROOT_HASH=e7c53f04bd88d29d075bfd1f62b073aeb69cbe09 -D_DEBUG 
-DDYNAMIC_ANNOTATIONS_ENABLED=1 -DENABLE_DISASSEMBLER 
-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_GDB_JIT_INTERFACE 
-DENABLE_MINOR_MC -DOBJECT_PRINT -DVERIFY_HEAP -DV8_TRACE_MAPS 
-DV8_ENABLE_ALLOCATION_TIMEOUT -DV8_ENABLE_FORCE_SLOW_PATH 
-DV8_ENABLE_DOUBLE_CONST_STORE_CHECK -DV8_INTL_SUPPORT 
-DENABLE_HANDLE_ZAPPING -DV8_USE_SNAPSHOT 
-DV8_SNAPSHOT_NATIVE_CODE_COUNTERS -DV8_USE_EXTERNAL_STARTUP_DATA 
-DV8_CONCURRENT_MARKING -DV8_ENABLE_LAZY_SOURCE_POSITIONS 
-DV8_CHECK_MICROTASKS_SCOPES_CONSISTENCY -DV8_EMBEDDED_BUILTINS 
-DV8_SHARED_RO_HEAP -DV8_WIN64_UNWINDING_INFO 
-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH -DV8_ENABLE_CHECKS 
-DV8_DEPRECATION_WARNINGS -DV8_IMMINENT_DEPRECATION_WARNINGS 
-DV8_TARGET_ARCH_X64 -DDEBUG -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DBUILDING_V8_SHARED -DV8_ENABLE_CHECKS -DV8_DEPRECATION_WARNINGS 
-DV8_IMMINENT_DEPRECATION_WARNINGS -DUSING_V8_BASE_SHARED -I../.. -Igen 
-I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 
-fstack-protector -funwind-tables -fPIC 
-B../../third_party/binutils/Linux_x64/Release/bin -pthread 
-fcolor-diagnostics -fmerge-all-constants 
-fcrash-diagnostics-dir=../../tools/clang/crashreports -Xclang -mllvm 
-Xclang -instcombine-lower-dbg-declare=0 -fcomplete-member-pointers -m64 

Re: [v8-users] Build V8 6.x on Windows with VS2013

[Ivan Pizhenko]

I have actually tried.
I picked V8 version from stable Chromium versions and tried to compile. V8
5.6 compiled (at least, to some extent, I was interested only to compiling
V8 DLLs itself, ICU DLLs and D8 executable - and all this actually
compiles).
V8 5.7 and  5.8 failed to compile with VS2013. I did not try to dig deeply
into source code why, but looks like VC2013 lacks some support for
constexpr inside class, because it failed on the
class   {

constexpr bool . ; // <<< FAILED HERE


<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2017-11-04 0:54 GMT+02:00 J Decker <d3c...@gmail.com>:

>
>
> On Fri, Nov 3, 2017 at 3:49 PM, Ivan Pizhenko <ivan.pizhe...@gmail.com>
> wrote:
>
>> Actually, from these ones:
>> {"chromium_version": "56.0.2924.121", "v8_version": "5.6.326.55"}
>> {"chromium_version": "57.0.2987.154", "v8_version": "5.7.492.73"}
>> {"chromium_version": "58.0.3029.125", "v8_version": "5.8.283.38"}
>> only V8 5.6 is buildable with VS2013.
>>
>> did you actually try?  Or just assume?  or just take notes from docs?
> I'd imagine it doesn't have a lot of differences that would cause it to
> break on slightly older VS versions... although not officially supported.
> https://github.com/v8/v8/wiki/Building%20with%20Gyp says 2013 is a
> compiler that you can use (no mention of 2017 though; maybe just outdated?)
>
>
>> 2017-11-01 17:12 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:
>>
>>> Thank you!
>>>
>>> 2017-11-01 13:26 GMT+02:00 Ben Noordhuis <i...@bnoordhuis.nl>:
>>>
>>>> On Wed, Nov 1, 2017 at 1:23 AM, Ivan P. <ivan.pizhe...@gmail.com>
>>>> wrote:
>>>> > Hello, I want to update V8 used in my application from the version
>>>> 5.3 to a
>>>> > some latest stable 6.x
>>>> > The possible issue is that my application is built with a bit outdated
>>>> > nowadays Visual Studio 2013 and in the meantime I cannot upgrade to
>>>> any
>>>> > later VS version due to some other pending dependencies.
>>>> > Can anyone of V8 developers, or just someone proficient in the topic,
>>>> tell
>>>> > me, whether latest V8 6.x still can be built with VS2013?
>>>> > (I could do it for the version I use now - some 5.3), and if not,
>>>> what is
>>>> > the last version of V8 that can be built with VS 2013?
>>>>
>>>> I'm fairly sure that 2013 is not tested or supported anymore, so the
>>>> answer to your first question is 'probably not.'
>>>>
>>>> The answer to your second question is V8 5.8 or thereabouts.
>>>>
>>>> --
>>>> --
>>>> v8-users mailing list
>>>> v8-users@googlegroups.com
>>>> http://groups.google.com/group/v8-users
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "v8-users" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>>> pic/v8-users/7G1IsFY3QLI/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> v8-users+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/7G1IsFY3QLI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Build V8 6.x on Windows with VS2013

[Ivan Pizhenko]

Actually, from these ones:
{"chromium_version": "56.0.2924.121", "v8_version": "5.6.326.55"}
{"chromium_version": "57.0.2987.154", "v8_version": "5.7.492.73"}
{"chromium_version": "58.0.3029.125", "v8_version": "5.8.283.38"}
only V8 5.6 is buildable with VS2013.

2017-11-01 17:12 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:

> Thank you!
>
> 2017-11-01 13:26 GMT+02:00 Ben Noordhuis <i...@bnoordhuis.nl>:
>
>> On Wed, Nov 1, 2017 at 1:23 AM, Ivan P. <ivan.pizhe...@gmail.com> wrote:
>> > Hello, I want to update V8 used in my application from the version 5.3
>> to a
>> > some latest stable 6.x
>> > The possible issue is that my application is built with a bit outdated
>> > nowadays Visual Studio 2013 and in the meantime I cannot upgrade to any
>> > later VS version due to some other pending dependencies.
>> > Can anyone of V8 developers, or just someone proficient in the topic,
>> tell
>> > me, whether latest V8 6.x still can be built with VS2013?
>> > (I could do it for the version I use now - some 5.3), and if not, what
>> is
>> > the last version of V8 that can be built with VS 2013?
>>
>> I'm fairly sure that 2013 is not tested or supported anymore, so the
>> answer to your first question is 'probably not.'
>>
>> The answer to your second question is V8 5.8 or thereabouts.
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "v8-users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/v8-users/7G1IsFY3QLI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Build V8 6.x on Windows with VS2013

[Ivan Pizhenko]

Thank you!

2017-11-01 13:26 GMT+02:00 Ben Noordhuis :

> On Wed, Nov 1, 2017 at 1:23 AM, Ivan P.  wrote:
> > Hello, I want to update V8 used in my application from the version 5.3
> to a
> > some latest stable 6.x
> > The possible issue is that my application is built with a bit outdated
> > nowadays Visual Studio 2013 and in the meantime I cannot upgrade to any
> > later VS version due to some other pending dependencies.
> > Can anyone of V8 developers, or just someone proficient in the topic,
> tell
> > me, whether latest V8 6.x still can be built with VS2013?
> > (I could do it for the version I use now - some 5.3), and if not, what is
> > the last version of V8 that can be built with VS 2013?
>
> I'm fairly sure that 2013 is not tested or supported anymore, so the
> answer to your first question is 'probably not.'
>
> The answer to your second question is V8 5.8 or thereabouts.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/7G1IsFY3QLI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: Linking V8 to app on Windows

[Ivan Pizhenko]

Edited gni/v8.gni as you recommended and trying to build with following
args.gn:

is_component_build = false
is_debug = true
v8_optimized_debug=false
target_cpu="x64"
v8_target_cpu="x64"

and getting following error:

ninja -j1 -C out.gn/x64.debug
ninja: Entering directory `out.gn/x64.debug'
[1/287] LINK v8_simple_json_fuzzer.exe
FAILED: v8_simple_json_fuzzer.exe
L:/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper
environment.x64 False link.exe /nologo /OUT:v8_simple_
json_fuzzer.exe /PDB:v8_simple_json_fuzzer.exe.pdb
@v8_simple_json_fuzzer.exe.rsp
LINK : warning LNK4044: unrecognized option '/fastfail'; ignored
LINK : error LNK2001: unresolved external symbol mainCRTStartup
v8_simple_json_fuzzer.exe : fatal error LNK1120: 1 unresolved externals

what I am doing wrong? please advice.

2016-11-16 0:01 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:

> Thaks, I will try this workaround, but also please tell me, what exactly
> do you mean by current development branch? Which version of V8 does it
> corresponds? 5.5?  5.6?
>
> 2016-11-10 20:33 GMT+02:00 Jochen Eisinger <joc...@chromium.org>:
>
>> on 5.3, it's not yet possible to build the libplatform as a shared
>> library (dll), sorry. This is fixed in the current development branch.
>>
>> also, by default we don't actually create static libraries, but gn just
>> keeps track of the object files you need. You can change that by manually
>> replacing source_set with static_library in the v8_source_set template in
>> gni/v8.gni
>>
>> hth
>> -jochen
>>
>> On Thu, Nov 10, 2016 at 3:37 PM Ivan Pizhenko <ivan.pizhe...@gmail.com>
>> wrote:
>>
>> So I would like to hear comments on this from some V8 developer or
>> whoever solved the issue w/o Nuget package.
>>
>> 2016-11-10 16:05 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:
>>
>> Thank you for advise, George, but what you suggest is not an option in
>> the my case, I need to have built from sources exactly this stable version
>> 5.3.332.45. There is no Nuget package fir exactly this version, and there
>> are also other circumstances those prevent me using  Nuget package. So I am
>> looking for exactly an explanation on how to solve this manually.
>>
>> 2016-11-09 19:36 GMT+02:00 George Marques <georgemje...@gmail.com>:
>>
>> I also had troubles with the build system. I found it's much easier to
>> just use this Nuget package: https://github.com/pmed/v8-nuget.
>>
>>
>> On Wednesday, November 9, 2016 at 5:42:19 AM UTC-2, Ivan P. wrote:
>>
>> Hello, I am porting my app from V8 3.19 to V8 5.3.332.45.
>> I have built new V8 version as DLL using Visual Studio 2013, updated code
>> of my app to use updated APIs  and now trying to perform full build of my
>> app.
>> My app doesn't use GN to build it, it is normal Visual Studio 2013
>> project. I have specified v8.dll.lib as additional linker input.
>>
>> I get following linker error:
>> 1>v8init.obj : error LNK2019: unresolved external symbol "class
>> v8::Platform * __cdecl v8::platform::CreateDefaultPlatform(int)"
>> (?CreateDefaultPlatform@platform@v8@@YAPEAVPlatform@2@H@Z) referenced in
>> function  "
>>
>> I suppose v8::platform::CreateDefaultPlatform() must be present in
>> libplatform, but because the error happens, I can make conclusion that
>> libplatform it is not included into v8.dll.lib.
>> I have examined V8 build outputs and couldn't find libplatform as
>> separate static lib or DLL: here is list of libs generated during the
>> build, here is what I have:
>>
>> icui18n.dll
>> icuuc.dll
>> msvcp120.dll
>> msvcp120d.dll
>> msvcr120.dll
>> msvcr120d.dll
>> pgort120.dll
>> v8.dll
>>
>>
>> cctest.lib
>> generate-bytecode-expectations.lib
>> icui18n.dll.lib
>> icuuc.dll.lib
>> mksnapshot.lib
>> unittests.lib
>> v8.dll.lib
>> v8_parser_shell.lib
>> v8_simple_json_fuzzer.lib
>> v8_simple_parser_fuzzer.lib
>> v8_simple_regexp_fuzzer.lib
>> v8_simple_wasm_asmjs_fuzzer.lib
>> v8_simple_wasm_fuzzer.lib
>>
>> Please advise - either how to tune build to have libplatform generated as
>> separate DLL or included to v8.dll ?
>> Or is it safe to make manually libplatform from obj files and link it,
>> taking into account v8 is DLL?
>>
>> Thanks.
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to a t

Re: [v8-users] Re: Linking V8 to app on Windows

[Ivan Pizhenko]

Thaks, I will try this workaround, but also please tell me, what exactly do
you mean by current development branch? Which version of V8 does it
corresponds? 5.5?  5.6?

2016-11-10 20:33 GMT+02:00 Jochen Eisinger <joc...@chromium.org>:

> on 5.3, it's not yet possible to build the libplatform as a shared library
> (dll), sorry. This is fixed in the current development branch.
>
> also, by default we don't actually create static libraries, but gn just
> keeps track of the object files you need. You can change that by manually
> replacing source_set with static_library in the v8_source_set template in
> gni/v8.gni
>
> hth
> -jochen
>
> On Thu, Nov 10, 2016 at 3:37 PM Ivan Pizhenko <ivan.pizhe...@gmail.com>
> wrote:
>
> So I would like to hear comments on this from some V8 developer or whoever
> solved the issue w/o Nuget package.
>
> 2016-11-10 16:05 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:
>
> Thank you for advise, George, but what you suggest is not an option in the
> my case, I need to have built from sources exactly this stable version
> 5.3.332.45. There is no Nuget package fir exactly this version, and there
> are also other circumstances those prevent me using  Nuget package. So I am
> looking for exactly an explanation on how to solve this manually.
>
> 2016-11-09 19:36 GMT+02:00 George Marques <georgemje...@gmail.com>:
>
> I also had troubles with the build system. I found it's much easier to
> just use this Nuget package: https://github.com/pmed/v8-nuget.
>
>
> On Wednesday, November 9, 2016 at 5:42:19 AM UTC-2, Ivan P. wrote:
>
> Hello, I am porting my app from V8 3.19 to V8 5.3.332.45.
> I have built new V8 version as DLL using Visual Studio 2013, updated code
> of my app to use updated APIs  and now trying to perform full build of my
> app.
> My app doesn't use GN to build it, it is normal Visual Studio 2013
> project. I have specified v8.dll.lib as additional linker input.
>
> I get following linker error:
> 1>v8init.obj : error LNK2019: unresolved external symbol "class
> v8::Platform * __cdecl v8::platform::CreateDefaultPlatform(int)"
> (?CreateDefaultPlatform@platform@v8@@YAPEAVPlatform@2@H@Z) referenced in
> function  "
>
> I suppose v8::platform::CreateDefaultPlatform() must be present in
> libplatform, but because the error happens, I can make conclusion that
> libplatform it is not included into v8.dll.lib.
> I have examined V8 build outputs and couldn't find libplatform as separate
> static lib or DLL: here is list of libs generated during the build, here is
> what I have:
>
> icui18n.dll
> icuuc.dll
> msvcp120.dll
> msvcp120d.dll
> msvcr120.dll
> msvcr120d.dll
> pgort120.dll
> v8.dll
>
>
> cctest.lib
> generate-bytecode-expectations.lib
> icui18n.dll.lib
> icuuc.dll.lib
> mksnapshot.lib
> unittests.lib
> v8.dll.lib
> v8_parser_shell.lib
> v8_simple_json_fuzzer.lib
> v8_simple_parser_fuzzer.lib
> v8_simple_regexp_fuzzer.lib
> v8_simple_wasm_asmjs_fuzzer.lib
> v8_simple_wasm_fuzzer.lib
>
> Please advise - either how to tune build to have libplatform generated as
> separate DLL or included to v8.dll ?
> Or is it safe to make manually libplatform from obj files and link it,
> taking into account v8 is DLL?
>
> Thanks.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/Y05xPj956Ys/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/Y05xPj956Ys/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: Linking V8 to app on Windows

[Ivan Pizhenko]

So I would like to hear comments on this from some V8 developer or whoever
solved the issue w/o Nuget package.

2016-11-10 16:05 GMT+02:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:

> Thank you for advise, George, but what you suggest is not an option in the
> my case, I need to have built from sources exactly this stable version
> 5.3.332.45. There is no Nuget package fir exactly this version, and there
> are also other circumstances those prevent me using  Nuget package. So I am
> looking for exactly an explanation on how to solve this manually.
>
> 2016-11-09 19:36 GMT+02:00 George Marques <georgemje...@gmail.com>:
>
>> I also had troubles with the build system. I found it's much easier to
>> just use this Nuget package: https://github.com/pmed/v8-nuget.
>>
>>
>> On Wednesday, November 9, 2016 at 5:42:19 AM UTC-2, Ivan P. wrote:
>>>
>>> Hello, I am porting my app from V8 3.19 to V8 5.3.332.45.
>>> I have built new V8 version as DLL using Visual Studio 2013, updated
>>> code of my app to use updated APIs  and now trying to perform full build of
>>> my app.
>>> My app doesn't use GN to build it, it is normal Visual Studio 2013
>>> project. I have specified v8.dll.lib as additional linker input.
>>>
>>> I get following linker error:
>>> 1>v8init.obj : error LNK2019: unresolved external symbol "class
>>> v8::Platform * __cdecl v8::platform::CreateDefaultPlatform(int)"
>>> (?CreateDefaultPlatform@platform@v8@@YAPEAVPlatform@2@H@Z) referenced
>>> in function  "
>>>
>>> I suppose v8::platform::CreateDefaultPlatform() must be present in
>>> libplatform, but because the error happens, I can make conclusion that
>>> libplatform it is not included into v8.dll.lib.
>>> I have examined V8 build outputs and couldn't find libplatform as
>>> separate static lib or DLL: here is list of libs generated during the
>>> build, here is what I have:
>>>
>>> icui18n.dll
>>> icuuc.dll
>>> msvcp120.dll
>>> msvcp120d.dll
>>> msvcr120.dll
>>> msvcr120d.dll
>>> pgort120.dll
>>> v8.dll
>>>
>>>
>>> cctest.lib
>>> generate-bytecode-expectations.lib
>>> icui18n.dll.lib
>>> icuuc.dll.lib
>>> mksnapshot.lib
>>> unittests.lib
>>> v8.dll.lib
>>> v8_parser_shell.lib
>>> v8_simple_json_fuzzer.lib
>>> v8_simple_parser_fuzzer.lib
>>> v8_simple_regexp_fuzzer.lib
>>> v8_simple_wasm_asmjs_fuzzer.lib
>>> v8_simple_wasm_fuzzer.lib
>>>
>>> Please advise - either how to tune build to have libplatform generated
>>> as separate DLL or included to v8.dll ?
>>> Or is it safe to make manually libplatform from obj files and link it,
>>> taking into account v8 is DLL?
>>>
>>> Thanks.
>>>
>>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "v8-users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/v8-users/Y05xPj956Ys/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: Linking V8 to app on Windows

[Ivan Pizhenko]

Thank you for advise, George, but what you suggest is not an option in the
my case, I need to have built from sources exactly this stable version
5.3.332.45. There is no Nuget package fir exactly this version, and there
are also other circumstances those prevent me using  Nuget package. So I am
looking for exactly an explanation on how to solve this manually.

2016-11-09 19:36 GMT+02:00 George Marques :

> I also had troubles with the build system. I found it's much easier to
> just use this Nuget package: https://github.com/pmed/v8-nuget.
>
>
> On Wednesday, November 9, 2016 at 5:42:19 AM UTC-2, Ivan P. wrote:
>>
>> Hello, I am porting my app from V8 3.19 to V8 5.3.332.45.
>> I have built new V8 version as DLL using Visual Studio 2013, updated code
>> of my app to use updated APIs  and now trying to perform full build of my
>> app.
>> My app doesn't use GN to build it, it is normal Visual Studio 2013
>> project. I have specified v8.dll.lib as additional linker input.
>>
>> I get following linker error:
>> 1>v8init.obj : error LNK2019: unresolved external symbol "class
>> v8::Platform * __cdecl v8::platform::CreateDefaultPlatform(int)"
>> (?CreateDefaultPlatform@platform@v8@@YAPEAVPlatform@2@H@Z) referenced in
>> function  "
>>
>> I suppose v8::platform::CreateDefaultPlatform() must be present in
>> libplatform, but because the error happens, I can make conclusion that
>> libplatform it is not included into v8.dll.lib.
>> I have examined V8 build outputs and couldn't find libplatform as
>> separate static lib or DLL: here is list of libs generated during the
>> build, here is what I have:
>>
>> icui18n.dll
>> icuuc.dll
>> msvcp120.dll
>> msvcp120d.dll
>> msvcr120.dll
>> msvcr120d.dll
>> pgort120.dll
>> v8.dll
>>
>>
>> cctest.lib
>> generate-bytecode-expectations.lib
>> icui18n.dll.lib
>> icuuc.dll.lib
>> mksnapshot.lib
>> unittests.lib
>> v8.dll.lib
>> v8_parser_shell.lib
>> v8_simple_json_fuzzer.lib
>> v8_simple_parser_fuzzer.lib
>> v8_simple_regexp_fuzzer.lib
>> v8_simple_wasm_asmjs_fuzzer.lib
>> v8_simple_wasm_fuzzer.lib
>>
>> Please advise - either how to tune build to have libplatform generated as
>> separate DLL or included to v8.dll ?
>> Or is it safe to make manually libplatform from obj files and link it,
>> taking into account v8 is DLL?
>>
>> Thanks.
>>
>> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/Y05xPj956Ys/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Memory allocation tracking in V8

[Ivan Pizhenko]

Thanks, This was useful.

2016-11-07 12:53 GMT+02:00 Jochen Eisinger :

> in general, you can check bit.ly/v8-api-changes to learn about
> replacements for deprecated and removed APIs
>
> On Mon, Nov 7, 2016 at 11:51 AM Michael Lippautz 
> wrote:
>
>> On Fri, Nov 4, 2016 at 4:01 PM Ivan P.  wrote:
>>
>> Hello, I am porting my app to latest stable version of the V8 engine from
>> quite legacy V8 3.19.
>> I was using v8::V8::AddMemoryAllocationCallback() to set callaback on
>> the memory allocation actions.
>> But now I can't find this function. What is analog to this in the new V8?
>> I am porting to version 5.3.332.45
>>
>>
>> AddMemoryAllocationCallback has been removed because its semantics were
>> not clearly defined.
>>
>> You can use Isolate::GetHeapSpaceStatistics from a combination of
>> (a) a GC epilogue callback registered using Isolate::AddGCEpilogueCallback
>> (b) an interrupt registered using Isolate::RequestInterrupt.
>>
>> For coarse-grained (up to a couple %) info (a) will be enough as the GC
>> will kick in if memory grows above certain limits. (b) is needed if you
>> want more fine-grained statistics.
>>
>> -Michael
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/Xcvt8E5KKkw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: How to build V8 on Linux using GCC instead of Clang?

[Ivan Pizhenko]

Tried this. I have following args.gn

is_debug=true
is_component_build=true
target_cpu="x64"
v8_target_cpu="x64"
v8_postmortem_support=true
is_clang=false
use_sysroot=false


and getting this error

Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
Package gmodule-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gmodule-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gmodule-2.0' found
Package gobject-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gobject-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gobject-2.0' found
Package gthread-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gthread-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gthread-2.0' found
Could not run pkg-config.

I am trying to build on the CentOS 7.
Updated OS with latest updates, installed package glib-devel.
What else is missing?


2016-09-28 15:36 GMT+03:00 'Michael Achenbach' via v8-users <
v8-users@googlegroups.com>:

> 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 г., 3:13:02 UTC+3 пользователь Ivan P. написал:
>>>
>>> I have set up depot tools and checked out latest stable V8 version from
>>> latest stable Chromium (V8 ver. 5.3.332.45) like this.
>>>
>>> fetch v8
>>> cd v8
>>> git checkout -b mybranch 5.3.332.45
>>> gclient sync
>>>
>>> I have generated build files using
>>>
>>> gn args gn.out/test1
>>>
>>> and run build as
>>>
>>> ninja -C gn.out/test1
>>>
>>> and I can see that V8 is being built using clang++.
>>>
>>> I want to build using g++.
>>>
>>> What should be changed, please advise.
>>>
>>> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/l-atCAMVHZU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

Thank you Pavel. This may be useful for me.

2016-09-18 10:45 GMT+03:00 Pavel Medvedev :

> Hi Ivan,
>
> I may suggest to try pre-built Nuget packages for V8:
>
> https://www.nuget.org/packages/v8-v120-x86/
> https://www.nuget.org/packages/v8-v120-x64/
> https://www.nuget.org/packages/v8-v140-x86/
> https://www.nuget.org/packages/v8-v140-x64/
>
> I have created them recently in order to manage V8 build issues on Windows.
>
> I use GYP in a Python script to build V8 libraries and Nuget packages, as
> you can see at https://github.com/pmed/v8-nuget
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/sY-ToMUC_4I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

Still following question: the build has produced me bunch of executables
like d8.exe, but I need to embed V8 into my application and therefore I
need either DLL or LIB, which are not generated - I have searched
x64.release directory for LIB files and all it found are following:
options_sources.lib
gmock.lib
gmock_main.lib
gtest.lib
icui18n.lib
icuuc.lib

but there are no v8_base.lib, v8_snapshot.lib and so on.

How to force build to generare V8 libs?


2016-09-16 16:40 GMT+03:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:

> Switched to VS2013 by using
> L:\v8-build\v8>set GYP_MSVS_VERSION=2013
>
> 2016-09-16 15:26 GMT+03:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:
>
>> And how to configure build to use exactly VS2013?
>> I have both VS2015 and VS2013 installed on the machine, but I need to use
>> VS2013.
>> However, after I have used
>> python tools/dev/v8gen.py x64.release
>> it seems to generate build parameters that use VS2015.
>> So what do I need to do to point it to the VS2013?
>>
>> 2016-09-16 15:16 GMT+03:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:
>>
>>> And which previous stable version can be surely built with VS2013?
>>> I don't need very latest version, but I need something stable and
>>> buildable with VS2013.
>>>
>>> 2016-09-16 9:35 GMT+03:00 Jochen Eisinger <joc...@chromium.org>:
>>>
>>>> Maybe? I'm using vs2015, no idea whether 2013 C++11 support is enough
>>>>
>>>> Ivan Pizhenko <ivan.pizhe...@gmail.com> schrieb am Fr., 16. Sep. 2016,
>>>> 08:30:
>>>>
>>>>> Got following output, seems like update succeeded, please confirm.
>>>>> Will I be able to build it with VS2013 now?
>>>>>
>>>>> L:\v8-build>set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>>>>>
>>>>> L:\v8-build>gclient sync
>>>>> Syncing projects: 100% (23/23), done.
>>>>>
>>>>>  running 'L:\depot_tools\python276_bin\python.exe
>>>>> v8/gypfiles/landmines.py' in 'L:\v8-build'
>>>>> Clobbering due to missing landmines file.
>>>>>
>>>>>  running 'download_from_google_storage --no_resume
>>>>> --platform=win32 --no_auth --bucket chromium-clang-format -s
>>>>> v8/buildtools/win/clang-format.exe.sha1' in 'L:\v8-build'
>>>>> 0> Downloading v8/buildtools/win/clang-format.exe...
>>>>> Success!
>>>>> Downloading 1 files took 11.732000 second(s)
>>>>> Hook 'download_from_google_storage --no_resume --platform=win32
>>>>> --no_auth --bucket chromium-clang-format -s v8/buildtool
>>>>> s/win/clang-format.exe.sha1' took 11.92 secs
>>>>>
>>>>>  running 'download_from_google_storage --no_resume
>>>>> --platform=darwin --no_auth --bucket chromium-clang-format -s
>>>>>  v8/buildtools/mac/clang-format.sha1' in 'L:\v8-build'
>>>>> The current platform doesn't match "darwin", skipping.
>>>>>
>>>>>  running 'download_from_google_storage --no_resume
>>>>> --platform=linux* --no_auth --bucket chromium-clang-format -s
>>>>>  v8/buildtools/linux64/clang-format.sha1' in 'L:\v8-build'
>>>>> The current platform doesn't match "linux*", skipping.
>>>>>
>>>>>  running 'L:\depot_tools\python276_bin\python.exe
>>>>> v8/tools/gcmole/download_gcmole_tools.py' in 'L:\v8-build'
>>>>> Skipping gcmole download as gcmole is not set in gyp flags.
>>>>>
>>>>>  running 'L:\depot_tools\python276_bin\python.exe
>>>>> v8/tools/jsfunfuzz/download_jsfunfuzz.py' in 'L:\v8-build'
>>>>> Skipping jsfunfuzz download as jsfunfuzz is not set in gyp flags.
>>>>>
>>>>>  running 'download_from_google_storage --no_resume
>>>>> --platform=win32 --no_auth --bucket chromium-luci -d v8/tools
>>>>> /luci-go/win64' in 'L:\v8-build'
>>>>> 0> Downloading v8/tools/luci-go/win64\isolate.exe...
>>>>> Success!
>>>>> Downloading 1 files took 12.466000 second(s)
>>>>> Hook 'download_from_google_storage --no_resume --platform=win32
>>>>> --no_auth --bucket chromium-luci -d v8/tools/luci-go/win
>>>>> 64' took 12.62 secs
>>>>>
>>>>>  running 'download_from_google_storage --no_resume
>>>>> --platform=darwin --no_auth --bucket chromium-luci -d v8/tool

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

And how to configure build to use exactly VS2013?
I have both VS2015 and VS2013 installed on the machine, but I need to use
VS2013.
However, after I have used
python tools/dev/v8gen.py x64.release
it seems to generate build parameters that use VS2015.
So what do I need to do to point it to the VS2013?

2016-09-16 15:16 GMT+03:00 Ivan Pizhenko <ivan.pizhe...@gmail.com>:

> And which previous stable version can be surely built with VS2013?
> I don't need very latest version, but I need something stable and
> buildable with VS2013.
>
> 2016-09-16 9:35 GMT+03:00 Jochen Eisinger <joc...@chromium.org>:
>
>> Maybe? I'm using vs2015, no idea whether 2013 C++11 support is enough
>>
>> Ivan Pizhenko <ivan.pizhe...@gmail.com> schrieb am Fr., 16. Sep. 2016,
>> 08:30:
>>
>>> Got following output, seems like update succeeded, please confirm.
>>> Will I be able to build it with VS2013 now?
>>>
>>> L:\v8-build>set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>>>
>>> L:\v8-build>gclient sync
>>> Syncing projects: 100% (23/23), done.
>>>
>>>  running 'L:\depot_tools\python276_bin\python.exe
>>> v8/gypfiles/landmines.py' in 'L:\v8-build'
>>> Clobbering due to missing landmines file.
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=win32 --no_auth --bucket chromium-clang-format -s
>>> v8/buildtools/win/clang-format.exe.sha1' in 'L:\v8-build'
>>> 0> Downloading v8/buildtools/win/clang-format.exe...
>>> Success!
>>> Downloading 1 files took 11.732000 second(s)
>>> Hook 'download_from_google_storage --no_resume --platform=win32
>>> --no_auth --bucket chromium-clang-format -s v8/buildtool
>>> s/win/clang-format.exe.sha1' took 11.92 secs
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=darwin --no_auth --bucket chromium-clang-format -s
>>>  v8/buildtools/mac/clang-format.sha1' in 'L:\v8-build'
>>> The current platform doesn't match "darwin", skipping.
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=linux* --no_auth --bucket chromium-clang-format -s
>>>  v8/buildtools/linux64/clang-format.sha1' in 'L:\v8-build'
>>> The current platform doesn't match "linux*", skipping.
>>>
>>>  running 'L:\depot_tools\python276_bin\python.exe
>>> v8/tools/gcmole/download_gcmole_tools.py' in 'L:\v8-build'
>>> Skipping gcmole download as gcmole is not set in gyp flags.
>>>
>>>  running 'L:\depot_tools\python276_bin\python.exe
>>> v8/tools/jsfunfuzz/download_jsfunfuzz.py' in 'L:\v8-build'
>>> Skipping jsfunfuzz download as jsfunfuzz is not set in gyp flags.
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=win32 --no_auth --bucket chromium-luci -d v8/tools
>>> /luci-go/win64' in 'L:\v8-build'
>>> 0> Downloading v8/tools/luci-go/win64\isolate.exe...
>>> Success!
>>> Downloading 1 files took 12.466000 second(s)
>>> Hook 'download_from_google_storage --no_resume --platform=win32
>>> --no_auth --bucket chromium-luci -d v8/tools/luci-go/win
>>> 64' took 12.62 secs
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=darwin --no_auth --bucket chromium-luci -d v8/tool
>>> s/luci-go/mac64' in 'L:\v8-build'
>>> The current platform doesn't match "darwin", skipping.
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=linux* --no_auth --bucket chromium-luci -d v8/tool
>>> s/luci-go/linux64' in 'L:\v8-build'
>>> The current platform doesn't match "linux*", skipping.
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=win32 --no_auth --bucket chromium-gn -s v8/buildto
>>> ols/win/gn.exe.sha1' in 'L:\v8-build'
>>> 0> Downloading v8/buildtools/win/gn.exe...
>>> Success!
>>> Downloading 1 files took 10.441000 second(s)
>>> Hook 'download_from_google_storage --no_resume --platform=win32
>>> --no_auth --bucket chromium-gn -s v8/buildtools/win/gn.e
>>> xe.sha1' took 10.62 secs
>>>
>>>  running 'download_from_google_storage --no_resume
>>> --platform=darwin --no_auth --bucket chromium-gn -s v8/buildt
>>> ools/mac/gn.sha1' in 'L:\v8-build'
>>> The current platform doesn't match "darwin", skipping.
>>>
>>>  running 'download_from_

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

And which previous stable version can be surely built with VS2013?
I don't need very latest version, but I need something stable and buildable
with VS2013.

2016-09-16 9:35 GMT+03:00 Jochen Eisinger <joc...@chromium.org>:

> Maybe? I'm using vs2015, no idea whether 2013 C++11 support is enough
>
> Ivan Pizhenko <ivan.pizhe...@gmail.com> schrieb am Fr., 16. Sep. 2016,
> 08:30:
>
>> Got following output, seems like update succeeded, please confirm.
>> Will I be able to build it with VS2013 now?
>>
>> L:\v8-build>set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>>
>> L:\v8-build>gclient sync
>> Syncing projects: 100% (23/23), done.
>>
>>  running 'L:\depot_tools\python276_bin\python.exe
>> v8/gypfiles/landmines.py' in 'L:\v8-build'
>> Clobbering due to missing landmines file.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=win32 --no_auth --bucket chromium-clang-format -s
>> v8/buildtools/win/clang-format.exe.sha1' in 'L:\v8-build'
>> 0> Downloading v8/buildtools/win/clang-format.exe...
>> Success!
>> Downloading 1 files took 11.732000 second(s)
>> Hook 'download_from_google_storage --no_resume --platform=win32 --no_auth
>> --bucket chromium-clang-format -s v8/buildtool
>> s/win/clang-format.exe.sha1' took 11.92 secs
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=darwin --no_auth --bucket chromium-clang-format -s
>>  v8/buildtools/mac/clang-format.sha1' in 'L:\v8-build'
>> The current platform doesn't match "darwin", skipping.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=linux* --no_auth --bucket chromium-clang-format -s
>>  v8/buildtools/linux64/clang-format.sha1' in 'L:\v8-build'
>> The current platform doesn't match "linux*", skipping.
>>
>>  running 'L:\depot_tools\python276_bin\python.exe
>> v8/tools/gcmole/download_gcmole_tools.py' in 'L:\v8-build'
>> Skipping gcmole download as gcmole is not set in gyp flags.
>>
>>  running 'L:\depot_tools\python276_bin\python.exe
>> v8/tools/jsfunfuzz/download_jsfunfuzz.py' in 'L:\v8-build'
>> Skipping jsfunfuzz download as jsfunfuzz is not set in gyp flags.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=win32 --no_auth --bucket chromium-luci -d v8/tools
>> /luci-go/win64' in 'L:\v8-build'
>> 0> Downloading v8/tools/luci-go/win64\isolate.exe...
>> Success!
>> Downloading 1 files took 12.466000 second(s)
>> Hook 'download_from_google_storage --no_resume --platform=win32 --no_auth
>> --bucket chromium-luci -d v8/tools/luci-go/win
>> 64' took 12.62 secs
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=darwin --no_auth --bucket chromium-luci -d v8/tool
>> s/luci-go/mac64' in 'L:\v8-build'
>> The current platform doesn't match "darwin", skipping.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=linux* --no_auth --bucket chromium-luci -d v8/tool
>> s/luci-go/linux64' in 'L:\v8-build'
>> The current platform doesn't match "linux*", skipping.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=win32 --no_auth --bucket chromium-gn -s v8/buildto
>> ols/win/gn.exe.sha1' in 'L:\v8-build'
>> 0> Downloading v8/buildtools/win/gn.exe...
>> Success!
>> Downloading 1 files took 10.441000 second(s)
>> Hook 'download_from_google_storage --no_resume --platform=win32 --no_auth
>> --bucket chromium-gn -s v8/buildtools/win/gn.e
>> xe.sha1' took 10.62 secs
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=darwin --no_auth --bucket chromium-gn -s v8/buildt
>> ools/mac/gn.sha1' in 'L:\v8-build'
>> The current platform doesn't match "darwin", skipping.
>>
>>  running 'download_from_google_storage --no_resume
>> --platform=linux* --no_auth --bucket chromium-gn -s v8/buildt
>> ools/linux64/gn.sha1' in 'L:\v8-build'
>> The current platform doesn't match "linux*", skipping.
>>
>>  running 'download_from_google_storage --no_resume --no_auth -u
>> --bucket v8-wasm-fuzzer -s v8/test/fuzzer/wasm.t
>> ar.gz.sha1' in 'L:\v8-build'
>> 0> Downloading v8/test/fuzzer/wasm.tar.gz...
>> 0> Extracting 646 entries from v8/test/fuzzer/wasm.tar.gz to
>> v8/test/fuzzer/wasm
>> Success!
>> Downloading 1 files took 12.357000 second(s)
>> Hook 'download_from_google_storage --no_resume --no_auth -u --bucket
>> v8-wa

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

build'
Gold plugin download not supported on windows.

 running 'L:\depot_tools\python276_bin\python.exe
v8/tools/clang/scripts/update.py --if-needed' in 'L:\v8-build'


 running 'L:\depot_tools\python276_bin\python.exe
v8/gypfiles/gyp_v8 --running-as-hook' in 'L:\v8-build'
GYP is now disabled by default in runhooks.

If you really want to run this, either run
`python gypfiles/gyp_v8` explicitly by hand
or set the environment variable GYP_CHROMIUM_NO_ACTION=0.



2016-09-16 8:07 GMT+03:00 Jochen Eisinger <joc...@chromium.org>:

> Please set the env variable DEPOT_TOOLS_WIN_TOOLCHAIN to 0 and try again
>
> On Thu, Sep 15, 2016 at 3:44 PM Ivan Pizhenko <ivan.pizhe...@gmail.com>
> wrote:
>
>> Actually, differs a bit but still similar to previous one.
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/sY-ToMUC_4I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

Actually, differs a bit but still similar to previous one.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Problem getting V8 sources

[Ivan Pizhenko]

I get the same error:


L:\v8-build>L:\\depot_tools\\python276_bin\\python.exe
v8/gypfiles/landmines.py



Please follow the instructions at
https://www.chromium.org/developers/how-tos/build-instructions-windows


Traceback (most recent call last):
  File "v8/gypfiles/landmines.py", line 245, in 
sys.exit(main())
  File "v8/gypfiles/landmines.py", line 232, in main
gyp_environment.set_environment()
  File "L:\v8-build\v8\gypfiles\gyp_environment.py", line 60, in
set_environment
vs_toolchain.SetEnvironmentAndGetRuntimeDllDirs()
  File "L:\v8-build\v8\gypfiles\vs_toolchain.py", line 44, in
SetEnvironmentAndGetRuntimeDllDirs
Update()
  File "L:\v8-build\v8\gypfiles\vs_toolchain.py", line 323, in Update
subprocess.check_call(get_toolchain_args)
  File "L:\depot_tools\python276_bin\lib\subprocess.py", line 540, in
check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command
'['L:\\depot_tools\\python276_bin\\python.exe',
'L:\\depot_tools\\win_toolchain\\
get_toolchain_if_necessary.py', '--output-json',
'L:\\v8-build\\v8\\gypfiles\\win_toolchain.json', '03a4e939cd325d6bc521
6af41b92d02dda1366a6']' returned non-zero exit status 1

2016-09-15 10:12 GMT+03:00 Jochen Eisinger :

> If you manually run L:\\depot_tools\\python276_bin\\python.exe
> v8/gypfiles/landmines.py what error message do you get?
>
> On Wed, Sep 14, 2016 at 4:11 PM Ivan P.  wrote:
>
>> I am attempting to get V8 sources to build on Windows, using VS2013. OS
>> is Win2008 Server R2 x64.
>> I have downloaded and updated depot_tools.
>>
>> Then I have started new cmd shell and did following:
>>
>> L:\>path L:\depot_tools;%PATH%
>>
>> L:\>mkdir v8-build
>>
>> L:\>cd v8-build
>>
>> L:\v8-build>fetch v8
>> Running: 'L:\depot_tools\python276_bin\python.exe'
>> 'L:\depot_tools\gclient.py' root
>> Running: 'L:\depot_tools\python276_bin\python.exe'
>> 'L:\depot_tools\gclient.py' config --spec 'solutions = [
>>   {
>> "managed": False,
>> "name": "v8",
>> "url": "https://chromium.googlesource.com/v8/v8.git;,
>> "custom_deps": {},
>> "deps_file": "DEPS",
>> "safesync_url": "",
>>   },
>> ]
>> '
>> Running: 'L:\depot_tools\python276_bin\python.exe'
>> 'L:\depot_tools\gclient.py' sync --with_branch_heads
>> Error: Command 'L:\\depot_tools\\python276_bin\\python.exe
>> v8/gypfiles/landmines.py' returned non-zero exit status 1 in
>> L:\v8-build
>> Traceback (most recent call last):
>>   File "L:\depot_tools\\fetch.py", line 353, in 
>> sys.exit(main())
>>   File "L:\depot_tools\\fetch.py", line 348, in main
>> return run(options, spec, root)
>>   File "L:\depot_tools\\fetch.py", line 342, in run
>> return checkout.init()
>>   File "L:\depot_tools\\fetch.py", line 142, in init
>> self.run_gclient(*sync_cmd)
>>   File "L:\depot_tools\\fetch.py", line 76, in run_gclient
>> return self.run(cmd_prefix + cmd, **kwargs)
>>   File "L:\depot_tools\\fetch.py", line 66, in run
>> return subprocess.check_output(cmd, **kwargs)
>>   File "L:\depot_tools\python276_bin\lib\subprocess.py", line 573, in
>> check_output
>> raise CalledProcessError(retcode, cmd, output=output)
>> subprocess.CalledProcessError: Command 
>> '('L:\\depot_tools\\python276_bin\\python.exe',
>> 'L:\\depot_tools\\gclient.py', 'sync', '--with_branch_heads')' returned
>> non-zero exit status 2
>>
>> What this error means and how to get rid of it?
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/v8-users/sY-ToMUC_4I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] V8 Flags

[Ivan Pizhenko]

2015-10-29 11:21 GMT+02:00 Jakob Kummerow :

> Most flags are for debugging and development


"Most flags are for debugging and development" - that's exactly what I need
them for.
In particular, I want to limit memory amount that Isolate can use.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: Move V8 Context from one Isolate to another

[Ivan Pizhenko]

Thank you for the good idea. This approach with JSON sounds like what I
need to accomplish my task.

2015-03-05 23:44 GMT+02:00 Flying Jester foolkingcr...@gmail.com:

 What exactly are you trying to accomplish with this?

 Copying a context would be a huge operation, if it's possible at all (I
 don't think it is).

 You are almost certainly better off encapsulating the state you want in
 JSON or through some API you come up with yourself, and then loading that
 in a new context.

 On Thursday, March 5, 2015 at 8:58:45 AM UTC-9, Ivan P. wrote:

 What about making copy/clone of context?

 4 бер. 2015 09:52, користувач Yang Guo yan...@chromium.org написав:
 
  A context is too deeply entangled into the isolate it belongs to, so
 moving the context but not the isolate is basically impossible with the
 current V8.
 
 
  On Sunday, March 1, 2015 at 9:29:49 PM UTC+1, Ivan P. wrote:
 
  Does anybody know - is there an easy way to move some v8::Conext that
 belongs to some v8::Isolate to another v8::Isolate, preserving complete
 current state?
  Or at least make its copy/clone in the another v8::Isolate.
 
  --
  --
  v8-users mailing list
  v8-u...@googlegroups.com
  http://groups.google.com/group/v8-users
  ---
  You received this message because you are subscribed to a topic in the
 Google Groups v8-users group.
  To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/v8-users/Hy-Z-i52K8I/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to
 v8-users+u...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

  --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 http://groups.google.com/group/v8-users
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups v8-users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/v8-users/Hy-Z-i52K8I/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Re: Move V8 Context from one Isolate to another

[Ivan Pizhenko]

What about making copy/clone of context?

4 бер. 2015 09:52, користувач Yang Guo yang...@chromium.org написав:

 A context is too deeply entangled into the isolate it belongs to, so
moving the context but not the isolate is basically impossible with the
current V8.


 On Sunday, March 1, 2015 at 9:29:49 PM UTC+1, Ivan P. wrote:

 Does anybody know - is there an easy way to move some v8::Conext that
belongs to some v8::Isolate to another v8::Isolate, preserving complete
current state?
 Or at least make its copy/clone in the another v8::Isolate.

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 http://groups.google.com/group/v8-users
 ---
 You received this message because you are subscribed to a topic in the
Google Groups v8-users group.
 To unsubscribe from this topic, visit
https://groups.google.com/d/topic/v8-users/Hy-Z-i52K8I/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.