That was my thought as well. However, when I successfully built V8 with CLANG and then tried to build our application with MSVC 2017 it failed in the link process with missing symbols. Rebuilding the same version of V8 with MSVC (and fixing a few compiler errors and warnings for that to work) produced new binaries that resolved the linker errors.
On Sunday, March 15, 2020 at 5:54:51 AM UTC-4, Ben Noordhuis wrote: > > On Sat, Mar 14, 2020 at 3:03 PM Chris Fischer <[email protected] > <javascript:>> wrote: > > > > I'd like to chime in for continued support of MSVC (with build > regression automated tests). We embed V8 in a large project with many > third party code components. Many of these components are not available as > source so building with CLANG is not viable. We currently use V8 as a > component build (DLL) but could also use V8 as a static library compiled > with /MD. In general, most of our third party software comes with these > too variants (static & dynamic libraries with /MD runtime). > > > > I'd be happy to help in contributing / maintaining MSVC support but > would need a primer on contributing and and some contacts as sounding > boards for feedback and brainstorming. > > > > Chris Fischer > > I don't have a stake in this and I don't want to derail the > conversation but the clang-cl frontend is ABI-compatible with cl.exe > these days, isn't it? You don't even need to use it for all of your > project, just V8. > -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/a9ebdebb-d54a-43f1-b9dc-b057c3f62c6d%40googlegroups.com.
