qtdeclarative

History

Kent Hansen c1c0b9c03c Don't build V8 as a static library In the future, we'll need to be able to export the V8 symbols from the QtDeclarative library, which requires compiling V8 straight in. It's not possible to achieve this using a static library. Change-Id: Ie9e31984d2c03639a311cef11ddd33ba0aa15fd9 Reviewed-on: http://codereview.qt.nokia.com/2187 Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>		2011-07-26 14:15:07 +02:00
..
Makefile.nonqt	Don't build V8 as a static library	2011-07-26 14:15:07 +02:00
README.txt	Allow v8 autotest to run without Qt	2011-06-10 11:53:56 +10:00
tst_v8.cpp	Variants should compare as equal	2011-07-01 08:32:43 +02:00
v8.pro	Don't build V8 as a static library	2011-07-26 14:15:07 +02:00
v8main.cpp	Variants should compare as equal	2011-07-01 08:32:43 +02:00
v8test.cpp	Variants should compare as equal	2011-07-01 08:32:43 +02:00
v8test.h	Variants should compare as equal	2011-07-01 08:32:43 +02:00

README.txt

The v8 tests are actually implemented in v8test.[h|cpp].  There are also QtTest
(tst_v8.cpp) and non-Qt (v8main.cpp) stubs provided to run these tests.  This
is done to allow the tests to be run both in the Qt CI system, and manually 
without a build of Qt.  The latter is necessary to run them against more exotic
build of V8, like the ARM simulator.

To build the non-Qt version of the tests, first build a debug or release V8 
library under src/3rdparty/v8 using scons, and then use the Makefile.nonqt
makefile selecting one of the following targets:
    release: Build the tests with -O2 and link against libv8
    debug: Build the tests with -g and link against libv8_g
    release-m32: Build the tests with -O2 -m32 and link against libv8
    debug-m32: Build the tests with -g -m32 and link against libv8_g