The reason it's libQtV8 instead of libv8 is that it currently contains a few Qt specific patches on top of v8.
Cheers, Lars On 10/5/11 12:44 PM, "ext Jedrzej Nowacki" <[email protected]> wrote: >Hi, > >On Tuesday 4. October 2011 15.41.42 ext Thiago Macieira wrote: >> This just occurred to me: our QtV8 library contains symbols in the "v8" >> namespace. That means applications and libraries cannot load other V8 >> implementations, since that would cause symbol clashes and catastrophic >> failures. >> >> One solution is to rename the namespace inside our build of V8. >I think it is the only valid solution. > >> Another is to declare our build the official V8 build and just rename >>the >> library to simply "v8" (libv8.so.0 on Linux). >On some systems v8 is shipped as libv8 (libv8-3.1.8.22 on my debian >machine), but of course it is a bit different version. > >> Questions: >> - how close to maintaining binary compatibility is the V8 project? >> Something in the works? Or completely out of the question? >As far I know binary and source compatibility are out of scope for V8 >project (but source compatibility breakages are really uncommon) > >Cheers, > Jędrek >_______________________________________________ >Qt5-feedback mailing list >[email protected] >http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
