| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
QScriptValue test suit was way too big, so it was difficult to maintain.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The QScriptValue autotest suite compiles about 24 min with MSVS2008,
which is unacceptable.
Tests were splited into a few files for better use of distributed
compilation.
Repeated calls to insert() and operator<<() where replaced by loops,
that should reduce time of code optimizing.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
|
| |
This test includes a source file which is almost half a megabyte
in size. When compiling with -O2, MSVC2008 can take over 20
minutes to link this test!
Turn off optimization, just for this test.
|
|
|
|
|
|
|
|
|
| |
tst_qscriptvalue_generated.cpp was generated by Jedrzej's generator
(see testgen subdirectory).
The idea is that the old isXXX and toXXX tests will be replaced entirely
by the auto-generated versions, but we keep them for now (with "_old"
suffix) until we are sure that the auto-generated versions cover everything.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes Qt work on VxWorks 6.6+ in native (kernel) mode.
* compiles with the WindRiver GNU toolchain (Linux only)
* works with QWS (tested with the VNC driver only)
* tested on PPC hardware and the x86 VxWorks simulator
* no q3support, no phonon, no webkit
* no QSharedMemory, no QSystemSemaphore, no QProcess
* only one QApplication instance (flat address space)
* filesystem support depends heavily on the quality of the native driver
* QLibrary is just a dummy to make plugins work at all
* qmake transparently creates VxWorks munching rules for static ctors
* made auto-test cope with missing OS features
A special note regarding the Q_FOREACH patch for dcc:
when calling foreach(a,c) with c being a function returning a container,
the compiler would generate 5 references to some labels (.LXXXX), which
are not there (so the linker complains in the end).
Seems like dcc doesn't really like the 'true ? 0 : <function call to get type>'
statement
Reviewed-By: Harald Fernengel
|
|
|