2016-04-23 12:16 GMT+03:00 deloptes <deloptes@...>: > Hi, > I'm looking for a way to test the vcardparser. It looks like there is a > small test utility in tdeabc and tdeac/vcardparser. > > tdeabc/vcardparser$ more README.testing > For testing the vcardparser there are some test files and a small testsuite > automatically checking for regressions. > ... > ... > > Now with cmake building in test dir > > ======== > mkdir test && cd test && cmake .. > cd tdeabc/vcardparser > > test/tdeabc/vcardparser$ make check > make: *** No rule to make target 'check'. Stop. > cd .. > test/tdeabc$ make check > make: *** No rule to make target 'check'. Stop. > ======== > > but doing the old automake (it does not compile for various reasons) > produces a Makefile in vcardparser that (almost) works > > ======== > cd tdelibs-trinity-14.0.3/tdeabc/vcardparser > make check > make testread testwrite testread2 > make[1]: Entering > directory '/opt/software_x64/KDE/TDE/tdelibs-trinity-14.0.3/tdeabc/vcardparser' > g++ -DHAVE_CONFIG_H -I. -I../.. -I../../dcop -I../../kjs -I../../tdecore -I../../tdeio/kssl -I../../tdeabc -I../../tdeabc -I../../dcop -I../../libltdl -I../../tdefx -I../../tdecore -I../../tdecore -I../../tdecore/network -I../../tdeui -I../../tdeio -I../../tdeio/tdeio -I../../tdeio/tdefile -I../.. -I/usr/share/tqt3/include -include > tqt.h -I. -I/opt/trinity/include -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT > testread.o -MD -MP -MF .deps/testread.Tpo -c -o testread.o testread.cpp > In file included from testread.cpp:33:0: > ../../tdeabc/vcardconverter.h:26:23: fatal error: addressee.h: No such file > or directory > #include "addressee.h" > ^ > compilation terminated. > Makefile:710: recipe for target 'testread.o' failed > make[1]: *** [testread.o] Error 1 > make[1]: Leaving > directory '/opt/software_x64/KDE/TDE/tdelibs-trinity-14.0.3/tdeabc/vcardparser' > Makefile:840: recipe for target 'check-am' failed > make: *** [check-am] Error 2 > ======== > > Furthermore cmake refuses to use the src dir and does not produce usable > Makefile for the test suite > > ======== > tdelibs-trinity-14.0.3$ cmake . > -- The C compiler identification is GNU 4.9.2 > -- The CXX compiler identification is GNU 4.9.2 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Found PkgConfig: /usr/bin/pkg-config (found version "0.28") > CMake Error at cmake/modules/TDEMacros.cmake:24 (message): > ################################################# > > Please use out-of-source building, like this: > > rm /opt/software/KDE/TDE/tdelibs-trinity-14.0.3/CMakeCache.txt > mkdir /tmp/tdelibs.build > cd /tmp/tdelibs.build > cmake /opt/software/KDE/TDE/tdelibs-trinity-14.0.3 [arguments...] > > ################################################# > Call Stack (most recent call first): > cmake/modules/TDEMacros.cmake:1534 (tde_message_fatal) > CMakeLists.txt:39 (include) > > > -- Configuring incomplete, errors occurred! > See > also "/opt/software/KDE/TDE/tdelibs-trinity-14.0.3/CMakeFiles/CMakeOutput.log". > ======== > > Let me know what you think about it and should we raise a bug to track and > fix it. > > thanks in advance > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-devel-unsubscribe@... > For additional commands, e-mail: trinity-devel-help@... > Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > The testing framework wasn't introduced with migration to cmake. I believe that autotools unittests are broken as well now... IMHO it would be great to bring unittesting back, but this is a bit tough tasks which will be likely postponed forever... I personally not familiar with cmake testing in general...