> Yep, that seems to be the case, and it is sufficient for all clients of V8 > that I know of.
I don't know what you definition of 'client' is in this context, but I for one use the static libv8 and would be very concerned if the option to build this was dropped. > There's no need to explicitly specify it as it's the default behavior > anyway. It sounds like you are saying the static lib is built by default. Is that true? It contradicts most everything else you say in this post. > Why do you need libv8.a in the first place? Look at d8.gyp for an example > how you can statically link against V8. It "just works". Generally speaking, > if you have a choice at all, you should opt for dynamic linking (i.e. shared > libraries). I am uncomfortable dynamically linking against projects in very active development. We are a small company with v8 running on half a dozen different servers. There is a high likely hood of breaking things by deploying an add but forgetting to deploy an updated shared lib. I am not aware that statically linking to a .so is possible. I scanned the d8.gyp file. I don't speak gyp but I did not see anything about this. -- Bryan White -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
