You could build a static version of v8 library, but that doesn't mean you can make the whole binary that links with it static.
I like how OSX does it. Each application ships with its own .dll/.so/.dylib files. Thus each application can have its own required version of whatever shared library it depends on. I think the same effect can be achieved on Linux based systems. The trick is using the linker (ld) -rpath switch to specify where the final binary should search for libraries. http://en.wikipedia.org/wiki/Rpath I've not tried it. I'm musing here. On Jan 10, 2013, at 9:12 AM, Matt Horsnell <[email protected]> wrote: > With the old scons build system you used to be able to build statically, what > changed? > > On Thursday, 10 January 2013 12:43:33 UTC, mschwartz wrote: > Comments 6 & 7 in your link are particularly interesting. The link in > comment 6 is a must read for anyone considering static linking on Linux. > > On Jan 10, 2013, at 4:27 AM, Stephan Beal <[email protected]> wrote: > >> On Thu, Jan 10, 2013 at 7:58 AM, Joe Millenbach <[email protected]> wrote: >> If I make a patch that added the option, could it be accepted? Or is >> this functionality that is not desired? >> >> FWIW: v8 uses networking classes in some of the debugging code, and on Linux >> the networking libraries cannot be linked statically (for voodoo reasons >> which i don't recall). This ticket suggests that one might also have >> problems when statically linking against pthreads on linux: >> http://sourceware.org/bugzilla/show_bug.cgi?id=10652 >> >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> http://gplus.to/sgbeal >> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users > > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
