On Linux (and other platforms using gcc) you could use the option visibility=default to expose all of libv8.so - that will make the shell build with the shared library, but increase the size of libv8.so by about 10% and provide other clients of libv8.so to use internal APIs.
Otherwise I am afraid that you are out of luck. There is no way of running the tests with a shared library, and there probably will not be in the foreseeable future. If we decide to turn the shell back to a simple sample without the additional test supporting options and threading it will be possible to build it with shared library support, but it will not be able to run tests. d8 will then be updated to run tests, but as d8 is heavily dependent on v8::internal:: stuff it will not be buildable with a shared library. Regards, Søren On Fri, Apr 8, 2011 at 11:57, Paweł Hajdan, Jr. <[email protected]>wrote: > 2011/4/8 Søren Gjesse <[email protected]> > >> I am afraid that from the isolates merge >> (r7271<http://code.google.com/p/v8/source/detail?r=7271>) >> building the sample shell using shared libraries does no longer work. This >> is due to the sample shell not using APIs internal to v8 which is not >> exported through include/v8.h. For testing isolates we needed thread support >> for running tests, and currently the developer shell d8 is not suited for >> running tests threads where added to the sample shell using internal V8 >> thread support. We have issue >> 1272<http://code.google.com/p/v8/issues/detail?id=1272>open on this. >> >> It is still possible to build the process sample using V8 in a shared >> library. >> > > Thank you. Can the tests be run with the process sample instead of the > shell sample? > > I just need the shell to run tests. This is for a Linux distribution, so V8 > is built as a shared library. > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
