On Sat, Feb 29, 2020 at 5:26 AM YQ Tian <tianyuqiu123...@gmail.com> wrote:> > Thank you for your reply. It is currently found that when I upgrade v8 to > 6.8, the dynamic_cast function of my other dynamic library will call the > has_unambiguous_public_base function in the v8 library. Normally, the C ++ > standard library should be called. This phenomenon is very strange. I Compile > the monolith version into multiple libraries according to the previous > compilation method. Use the following command > > `gn gen out.gn/x64.release --args='is_debug=false target_cpu="x64" > v8_static_library=true v8_use_external_startup_data=false'` > > `ninja -C out.gn/x64.release` > > However, when the v8 library is introduced into the program, a link error > occurs. Some symbols like c ++ abi cannot be linked. Will the upgrade you > said solve this problem? Or do my compilation commands need to be modified?
V8 links to its own copy of libc++ unless told otherwise. I believe it's the use_custom_libcxx=false option. -- -- 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/CAHQurc-84RQPSg%2BVb8XcdAmDWydHiriL62YwxECn%2BTDacfzARQ%40mail.gmail.com.
