Comment #3 on issue 594 by [email protected]: Better handling of SONAME
http://code.google.com/p/v8/issues/detail?id=594
I am not sure that using V8 as a shared object is even a good idea. The V8
interface
is in C++ and when compiled the code will be split between the client and
the shared
object, that is not all the V8 code will actually be sitting in the shared
object.
Also inlining is used in the v8.h file and it is possible that there will
be a
mismatch if the client application is compiled with a different compiler
than the
shared object.
I will suggest that applications using V8 link statically to it.
Currently the SONAME generated by the SCons script is just using the full
version of
the trunk as specified in src/version.cc. There is the ability to set a
specific
SONAME in src/version.cc, which we could set and update manually whenever
there is a
(non trivial?) change in include/v8.h. However, the concerns above still
apply.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
