qt5base-lts/tests/auto/v8
Kent Hansen ce5adc7684 Revert "Update V8"
This reverts commit 1c4a5fcab76d1b769a4c0369d40dd0dd7c0e7495

Several of the qtdeclarative tests and examples are dying randomly with messages like this:
> 
> #
> # Fatal error in ../3rdparty/v8/src/objects-inl.h, line 2169
> # CHECK(object->IsJSFunction()) failed
> #
> 
> 
> ==== Stack trace ============================================
> 
> 
> ==== Details ================================================
> 
> ==== Key         ============================================
> 
> =====================
> 
> Aborted (core dumped)

Change-Id: Iebaa2497a6f6ef616ef4c3576c217d2a8a2c1ea5
Reviewed-by: Kent Hansen <kent.hansen@nokia.com>
2011-10-20 13:30:26 +02:00
..
Makefile.nonqt Add QtV8 library to QtBase 2011-08-29 10:16:01 +02:00
README.txt Add QtV8 library to QtBase 2011-08-29 10:16:01 +02:00
tst_v8.cpp Revert "Update V8" 2011-10-20 13:30:26 +02:00
v8.pro Fix autotest gui/widgets dependencies 2011-09-19 10:24:25 +02:00
v8main.cpp Revert "Update V8" 2011-10-20 13:30:26 +02:00
v8test.cpp Revert "Update V8" 2011-10-20 13:30:26 +02:00
v8test.h Revert "Update V8" 2011-10-20 13:30:26 +02:00

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