Re: [v8-users] How can I resolve or workaround this undefined symbol, building V8 on Windows 10, MSVC++2017?

2019-10-30 Thread Jakob Kummerow
If I had to guess: unibrow::ToUppercase::Convert in src/strings/unicode.h needs a V8_EXPORT_PRIVATE annotation in order to support the specific combination of building (1) cctests (2) on Windows (3) with is_component_build = true and (4) with v8_enable_i18n_support = false. If that theory is

[v8-users] How can I resolve or workaround this undefined symbol, building V8 on Windows 10, MSVC++2017?

2019-10-30 Thread Ben Ernst
I am building V8 7.8 (Windows 10, MSVC++ 2017) . My arguments to "GN" are as follows: treat_warnings_as_errors=false is_component_build=true v8_enable_i18n_support=false v8_use_snapshot=true I invoke ninja as follows. ninja -C out.gn/x64.release I encounter the below error toward the end of

Re: [v8-users] What do these unresolved external symbols mean when building against V8 7.8 "monolithic"?

2019-10-30 Thread Ben Ernst
Simon Thank you, I will try that solution today. Ben On Wednesday, 30 October 2019 18:40:42 UTC+10:30, Simon Zünd wrote: > > Best guess, you linked the V8 monolith static library with the libstdc++ > thats pulled in by "gclient sync". The project itself is linked against the > standard library

Re: [v8-users] What do these unresolved external symbols mean when building against V8 7.8 "monolithic"?

2019-10-30 Thread 'Simon Zünd' via v8-users
Best guess, you linked the V8 monolith static library with the libstdc++ thats pulled in by "gclient sync". The project itself is linked against the standard library of Visual Studio. There is a GN option for this, try "use_custom_libcxx = false", which will build V8 with the system C++ standard