[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: qt-dbus compilation problem
From:       Ralf Habacker <ralf.habacker () freenet ! de>
Date:       2006-06-01 19:39:17
Message-ID: 447F4265.4060101 () freenet ! de
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thiago Macieira schrieb:
> Ralf Habacker wrote:
>> This wrappers couold be avoided if all binaries and shared libraries
>> lives in <buildroot>/bin
> 
> I'll let the buildsystem take care of that. If a wrapper script is 
> necessary, then the buildsystem shall create one for me.

seems that cmake does not support this for win32 yet. I limited my
patches bin to win32, so unix isn't affected.

> 
>> cmakes provided test suite enables to produce this
>>
>> C:\Daten\kde4\kdesupport\qt-dbus-build>make test
>> Running tests...
>> Start processing tests
>> Test project
>>  1/  6 Testing tst_qdbusconnection           ***Failed
>>  2/  6 Testing tst_qdbusmarshall             ***Failed
>>  3/  6 Testing tst_qdbusxmlparser               Passed
>>  4/  6 Testing tst_qdbusinterface            ***Failed
>>  5/  6 Testing tst_qdbusabstractadaptor         Passed
>>  6/  6 Testing tst_hal                       ***Failed
>>
>> 33% tests passed, 4 tests failed out of 6
> 
> Considering there are a lot more tests in qdbusmarshal than tst_hal, the 
> number is blatantly false.
> 
> I'd much rather get the output of tst_xxxx -xml and create a proper 
> webpage.
> 
> But, as a simple wrapper to run them in the correct order, I don't see a 
> problem.

Which order is required ?

> 
>> The following tests FAILED:
>>          1 - tst_qdbusconnection (Failed)
>>          2 - tst_qdbusmarshall (Failed)
>>          4 - tst_qdbusinterface (Failed)
>>          6 - tst_hal (Failed)
>> Errors while running CTest
>> mingw32-make: *** [test] Error 8
> 
> Would be better if CTest integrated with QtTestLib to find out *which* 
> tests are available and, therefore, report the error count by test 
> function, not test program.

I have opened a requestion to the cmake gurus. Hope we get an answer. :-)


Ralf


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEf0JloHh+5t8EXncRAnxaAJ40LmrMa4K5xjbqB09zZ/Sxt9aC7wCgg5jk
Sul1h4vxU1FVex1kiytz2rQ=
=2+il
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]