I was able to build V8 on VS2022 version 17.3 (on another computer). I cannot build V8 on VS2022 version 17.5.1 (tested on multiple co-workers' computers). I wonder if something might have changed between these versions of MSVS that prevents the V8 build system from finding the libraries and headers. If anyone has any advice to help figure this out I would appreciate it.
On Wednesday, March 1, 2023 at 2:17:04 PM UTC+10:30 Ben Ernst wrote: > I am certain that you are correct, my system libc++ (MSVC) is for some > reason not found. It is definitely present. Is there any reason that the V8 > build system might fail to find it? > > On Tuesday, February 28, 2023 at 9:05:35 PM UTC+10:30 Ben Noordhuis wrote: > >> On Tue, Feb 28, 2023 at 3:15 AM Ben Ernst >> <ben.ernst....@gmail.com> wrote: >> > >> > use_custom_libcxx=false >> > >> > [snip] >> > >> > [exec] cl : Command line warning D9025 : overriding '/std:c++20' with >> '/std:c++17' >> > [exec] C:\88082ece\v8\include/cppgc/allocation.h(8): fatal error C1083: >> Cannot open include file: 'atomic': No such file or directory >> >> The warning is probably harmless. The fatal error is most likely >> caused by use_custom_libcxx=false. That tells V8 to use your system's >> libc++ instead of the bundled one but yours is either missing, not >> found, or missing some files. >> >> A caveat to keep in mind: you can't mix different libc++s. If you >> switch to V8's copy, you have to use it in your application as well. >> (How is left as an exercise; there are several ways to go about it.) >> > -- -- v8-dev mailing list v8-dev@googlegroups.com 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 v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/9067d137-d976-4a85-88d3-857423759c80n%40googlegroups.com.
