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

> I'll try compiling with "is_clang = true" Shouldn't hurt, although my suspicion is since you didn't override it, it defaulted to true, due to these lines from "build/config/BUILDCONFIG.gn": is_clang = current_os != "linux" || (current_cpu != "s390x" && current_cpu != "s390" &&

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

OP should also take a look at this thread https://groups.google.com/forum/#!topic/v8-users/Jb1VSouy2Z0 I'm facing the same linking issue on using v8 shared libs on CentOS 8 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this

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

While you wait for someone *much* more knowledgeable to reply... :-) I'm not brave enough to build on Windows, but presumably many things are similar. > I'm following the guide. More than one guide (or parts of guide) to follow! :-) Maybe you followed this one: https://v8.dev/docs/embed In

[v8-users] Re: Centos 8 Build failure.

I built v8(static v8_monolith) 7.9.317.32 on Centos 8 using clang. Building with GCC ie; is_clang=false causes trouble. It is not an officially supported configuration. On Monday, October 14, 2019 at