office-gobmx/testtools
Kurt Zenker b5cd26f743 INTEGRATION: CWS jl104 (1.1.4); FILE ADDED
2008/06/19 10:04:13 jl 1.1.4.2: #i88078# moving tests from cli_ure to testtools
2008/04/11 08:53:44 jl 1.1.4.1: file version_2_3.dll was added on branch cws_dev300_jl104 on 2008-06-19 10:04:13 +0000
2008-06-25 10:58:55 +00:00
..
com/sun/star/comp/bridge INTEGRATION: CWS changefileheader (1.6.44); FILE MERGED 2008-04-11 11:21:56 +00:00
inc INTEGRATION: CWS changefileheader (1.2.56); FILE MERGED 2008-04-11 11:22:50 +00:00
prj INTEGRATION: CWS jl104 (1.17.28); FILE MERGED 2008-06-25 10:49:38 +00:00
qa INTEGRATION: CWS jl104 (1.1.4); FILE ADDED 2008-06-25 10:50:05 +00:00
source INTEGRATION: CWS jl104 (1.1.4); FILE ADDED 2008-06-25 10:58:55 +00:00
readme.txt INTEGRATION: CWS jl97 (1.1.2); FILE ADDED 2008-05-05 15:33:59 +00:00

How to check compatibility between compilers
============================================

Since the interfaces used in the cpp bridgetest are not changed often
one can just build the cppobj.uno.dll and the constructors.uno.dll
(testtools/source/bridgetest) in an 
old environment and then use them in the new environment. That is the files 
are copied into the testtools/wntmsciXX.pro folder which corresponds to the 
new environment.

On Windows this test will typically fail because the tests use the 
cppu::getCaughtException function, which only works when all libs are build 
using the same runtime.

This part of the test can switched off. To do this go into the 
testtools/source/bridgetest folder and call
dmake compcheck=1

This will add a new compiler define (-DCOMPCHECK) and will be used in the 
bridgetest.cxx to switch off the code which uses the getCaughtException function.
However, there is still a test which causes the test component to throw
and IllegalArgumentException. This still works.