On Sat, Apr 28, 2018 at 7:25 PM, A.M. <cis74...@gmail.com> wrote: > Thanks for responding, Ben. Your feedback is always appreciated. > >> but apropos (2), >> the CRT linking logic is effectively hard-coded in >> build/config/win/BUILD.gn; > > This is surprising - it makes the static build of v8 quite expensive and > error-prone to maintain for a multi-DLL project, given that hundreds of > implementation callbacks would have to be implemented with `extern "C"` > linkage, as none of the STL, etc stuff can be shared between DLLs. > >> You could try >> sending a CL that adds a build flag to override the default or simply >> patch the file locally. > > If this is hard-coded in this day and age, it makes me think that Google did > it for a reason that I may not realize until I'm too deep into the project. > > May be I should switch to Chakra for this project. It's not as fast as the > v8, but there will be no compatibility issues when running multi-threaded > JavaScript within a Node process.
The reason is probably that V8 is designed to be shipped as part of a monolithic binary (Chromium, Node.js) rather than a standalone library. Dynamically linking to the CRT there doesn't gain you much and you lose some in predictability and reproducibility. From a QA perspective, it's great to have full control over all your components. -- -- 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.
