On Tue, Mar 19, 2019 at 2:02 AM 'Steven Johnson' via v8-users <v8-users@googlegroups.com> wrote: > > Are the details of how `use_custom_libcxx` should be set documented anywhere? > It appears that the default for the `x64.optdebug` and `x64.debug` builds is > to set this to true; this can cause amusing crashes if you link the resulting > dynamic library into an executable that is linked against the 'standard' > libc++/libstdc++ for the platform, at least on a fairly vanilla OSX system. > > (Looking thru the archives, I see a few threads referencing the issue, but > it's not clear to me which of the build settings are related to this issue... > or, more interestingly, why libV8 defaults to using a custom libc++ in the > first place. I'd be curious to know more about this decision.)
I expect it's because Chromium does it and they do it because it lets them use C++14 stdlib features (and probably C++17 too now.) If you stick with the platform's libc++, you're stuck with the lowest common denominator. To answer your other question, passing `use_custom_libcxx=false` to tools/dev/v8gen.py is probably what you want to do. The settings in tools/node/build_gn.py are likely also good defaults for other downstream users of V8 that aren't Chromium. -- -- 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. For more options, visit https://groups.google.com/d/optout.
