Thanks for the inputs, appreciate it immensely. i tried to build the V8 using Clang but as a shared dll, though the build was successful without any issues. but when i tried to link the dll and headers it generated few compiler errors
Based on the suggestions, we started using clang to build V8 on windows, but there is a problem, the V8 uses the Chromium's implementation of the STL, so when importing the header files in windows, we get the linker errors , because windows uses its own version of STL. class std::__Cr::unique_ptr<class v8::Platform,struct std::__Cr::default_delete<class v8::Platform> > __cdecl v8::platform::NewDefaultPlatform(int,enum v8::platform::IdleTaskSupport,enum v8::platform::InProcessStackDumping,class std::__Cr::unique_ptr<class v8::TracingController,struct std::__Cr::default_delete<class v8::TracingController> >,enum v8::platform::PriorityMode) how do we fix this. On Thursday, October 17, 2024 at 1:27:35 PM UTC+5:30 Ben Noordhuis wrote: > On Wed, Oct 16, 2024 at 9:38 PM Ben Ernst <boi...@gmail.com> wrote: > > > > Is it necessary to use clang for the whole program? > > In my (admittedly limited) testing clang-cl is ABI-compatible enough > that you can build the V8 .lib with clang-cl and link it against code > built with msvc. > > I suppose you could still run into language constructs in the header > files that msvc doesn't understand or misparses. > -- -- 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/0256ed87-ee2d-4077-a5c3-cd7d86ba1aacn%40googlegroups.com.
