I might have a similar issue but im on linux. At least in my case, the problem is that at "some" point since 6.5, v8's build config for "v8_static_library" starts to do thin archive vs the fat archive(which is more "static"). I've filed a bug but I haven't had time to track down the offending commit as they asked.
I don't know if it is for sure the same problem on windows. So just an FYI. On Wednesday, August 29, 2018 at 7:08:59 AM UTC-7, Quan Chen wrote: > > I'm having the same issue now. And same to you I'm trying to build the > static libs of V8. Have you come up with any solution? > > On Thursday, June 21, 2018 at 2:32:26 PM UTC+8, Amaranth F wrote: >> >> I use this parameter to generate the ninja project: >> >> gn gen out/Release "--args=is_debug=false target_cpu=\"x64\" >> v8_static_library=true v8_use_snapshot=true >> v8_use_external_startup_data=false" >> >> and then run: >> >> ninja -C out\Release >> >> when it finally says: >> >> ninja: Entering directory `out\Release' >> [1/58] LINK cctest.exe cctest.exe.pdb >> FAILED: cctest.exe cctest.exe.pdb >> G:/program/v8new3/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe >> ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x64 >> False ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo >> /OUT:./cctest.exe /PDB:./cctest.exe.pdb @./cctest.exe.rsp >> G:\program\v8new3\v8\third_party\llvm-build\Release+Asserts\bin\lld-link.exe: >> >> error: <root>: undefined symbol: mainCRTStartup >> >> How can I compile it, please? >> > -- -- v8-users mailing list [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
