24 Apr
2016
24 Apr
'16
1:52 p.m.
Michele Calgaro wrote:
Hi Emanoil,
I have not looked at this in detail, but at first sight the tdeabc/tests
folder does not contain any CMakeList.txt. In my log file in fact, I do
not find any reference to tde/tests, not surprisingly. You could try
adding a CMakeList.txt file and see what happens. Regarding tdeunittest, I
see in the build log that it gets built. Nevertheless trying to run it
from CLI (/opt/trinity/bin/tdeunittestmodrunner) gives a not so good "#
Running normal tests... # All 0 tests passed" output, suggesting no tests
have been run at all. I have never used it before, so perhaps I am doing
something wrong, but it is quite possible that instead it is broken as
Fat-Zer suggested.
Cheers
Michele
Ah, thanks, this is exactly what I was looking for. It has been a couple of
years since I last created CMakeList.txt . I think I would need a refresh
of this part of my memory - it wasn't thaaaat hard as the automake stuff.
From what I understood the test suite can be used prior to installation and
this would be handy in the case I have.
The tests included are idiotic, as there is no single non ascii char in
them - but perhaps utf was on non of the devices 10-15 years ago.
I think one has to first have the binary and test material in the right
place and do the testing after this, but cmake requires directory different
than project root. There might be also something in Fat-Zers statement.
Ufff - anyway - thanks for the hint.
New query:
1. Is there a good way to convert the Makefile.am into CMakeList.txt?
2. Is there an alternative way to test the library with the function of
interest without installing it?
I lack time and experience for this specific case.
BTW I just pulled tdelibs from git and got all recent fixes - it works
great. Thanks for the regex on the datetime issue - it's also very nice.
regards
regards