On Fri, Apr 8, 2011 at 12:42, Søren Gjesse <[email protected]> wrote:
> 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. > Right, this indeed made it compile. > 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. Could you consider another testing strategy then? V8 is not just used by Google Chrome the web browser. It is used by MongoDB, Node.js and probably other projects too. Linux distributions want to ship it as a shared library, and they want to run tests to make sure they pass (and a JS engine is non-trivial code, so it's really important; recently I've seen V8 test failures on arm-hardfloat, and they were detecting real issues). -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
