On 27/07/2012 15:03, Floren Munteanu wrote: > On Friday, July 27, 2012 8:19:44 AM UTC-4, kapouer wrote: > > The version you use in the package name (libv8-3.10.8) reflects the > soname version of the library. Upstream v8 doesn't guarantee ABI > compatibility of libv8 releases (because it is quite difficult to do so), > but, as indicated by data like > http://www.upstream-tracker.org/versions/v8.html > <http://www.upstream-tracker.org/versions/v8.html> > you can safely assume the soname version to be 3.10.8 instead of > 3.10.8.23, > because 3.10.8.24 (most likely) won't break ABI/API compatibility. > > If you understand this, you realize you can't choose a soname version of > 3.12.16, because it is likely to be ABI/API incompatible with 3.12.16.xx > at some point. In that case you either use the full version, or wait for > that branch to reach a stable state. > > > Thank you. That is another part of the gyp compiling puzzle I addressed. > Linux expects something like libv8.so.3 and I additionally provide soft links > for libv8.so, libv8.so.3.11 and libv8.so.3.11.10.
do you use the right flags ? here are the ones used in the debian package : library=shared snapshot=off soname_version=3.11.10 i advise you to look at the source package of others distros. Jérémy. -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
