I dynamically link in debug builds for the speed benefit, but for 
production deployments it is vastly easier to manage a statically-linked 
binary.

Moreover, if v8 is dynamically linking to a different C++ standard library 
/ runtime than my main app, that is likely to cause some subtle problems 
since the two runtimes will be maintaining separate state. Dynamic linking 
only masks the issue.

-Kenton

On Friday, September 8, 2017 at 2:57:33 PM UTC-7, Zac Hansen wrote:
>
> I don't have an answer for your specific question, but I highly recommend 
> dynamically linking to V8.   if nothing else it speeds up link times by 
> quite a bit, from what I remember from a while ago when I switched over.
>
> On Friday, September 8, 2017 at 8:52:17 AM UTC-7, Kenton Varda wrote:
>>
>> Hi v8-users,
>>
>> My C++ server app statically links against v8.
>>
>> My build broke when updating from 6.0 to 6.1. It looks like V8 now pulls 
>> in and builds libc++ as part of its own build. However, no libc++.a is 
>> generated, nor are the libc++ objects included in the regular static 
>> library outputs. So, naturally, I get link errors.
>>
>> I tried manually linking in the libc++ object files, but this reveals a 
>> second problem: I also link against the system-installed libprotobuf, which 
>> uses libstdc++. As libprotobuf uses std types in its ABI (my bad), this 
>> means my app needs to be linked against libstdc++ as well. I can't 
>> statically link against both C++ libs as this produces duplicate symbols.
>>
>> Is there a recommended approach to take here? Can I tell v8 to use 
>> libstdc++? Or do I need to vendor in libprotobuf so that I can build 
>> everything against libc++ from here on out?
>>
>> Thanks,
>> -Kenton
>>
>

-- 
-- 
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.

Reply via email to