1How to check compatibility between compilers 2============================================ 3 4Since the interfaces used in the cpp bridgetest are not changed often 5one can just build the cppobj.uno.dll and the constructors.uno.dll 6(testtools/source/bridgetest) in an 7old environment and then use them in the new environment. That is the files 8are copied into the testtools/wntmsciXX.pro folder which corresponds to the 9new environment. 10 11On Windows this test will typically fail because the tests use the 12cppu::getCaughtException function, which only works when all libs are build 13using the same runtime. 14 15This part of the test can switched off. To do this go into the 16testtools/source/bridgetest folder and call 17dmake compcheck=1 18 19This will add a new compiler define (-DCOMPCHECK) and will be used in the 20bridgetest.cxx to switch off the code which uses the getCaughtException function. 21However, there is still a test which causes the test component to throw 22and IllegalArgumentException. This still works. 23 24 25Using source/bridgetest for stress testing 26========================================== 27 28Start a modified bridgetest_server (with the final "--singleaccept" argument 29removed from the uno executable call) or a modified bridgetest_javaserver (with 30the final "singleaccept" argument replaced with "multi" in the java executable 31call), then start a modified bridgetest_client (with a final "stress" argument 32added to the uno executable call). The client will continuously establish 33connections to the server which are immediately destroyed again. The test will 34run forever, unless an error occurs. 35