Used following configuration (few of these are repeating, kept it that way, just to not miss anything):
use_custom_libcxx_for_host = false treat_warnings_as_errors = false v8_enable_i18n_support = false v8_enable_slow_dchecks = false is_component_build = false use_custom_libcxx = false v8_static_library = true v8_target_cpu = "x64" target_cpu = "x64" is_debug = false is_clang = false and targeted build for V8 and the resultant libraries are healthy and likable by VS2017. command to target build for V8: ninja -C out.gn\x64.release V8 On Tuesday, August 14, 2018 at 11:54:00 AM UTC-7, [email protected] wrote: > > V8 build failing for static libs on windows: VS 2017, Windows 10 > > > > > *FAILED: cctest.exe cctest.exe.pdbninja -t msvc -e environment.x64 -- > ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo > /OUT:./cctest.exe /PDB:./cctest.exe.pdb > @./cctest.exe.rsp../../third_party/llvm-build/Release+Asserts/bin\lld-link.exe: > > error: <root>: undefined symbol: mainCRTStartupninja: build stopped: > subcommand failed.* > > Build process does create libs but when try to link these to any project: > > *out.gn <http://out.gn>\x64.release\obj\v8_base.lib : fatal error LNK1127: > library is corrupt* > > Same results for ia32 target cpu. > > > > > *FAILED: cctest.exe cctest.exe.pdbninja -t msvc -e environment.x86 -- > ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo > /OUT:./cctest.exe /PDB:./cctest.exe.pdb > @./cctest.exe.rsp../../third_party/llvm-build/Release+Asserts/bin\lld-link.exe: > > error: <root>: undefined symbol: _mainCRTStartupninja: build stopped: > subcommand failed.* > > Any help would be appreciated. > > Thanks > Ajit > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
