<br><br><div class="gmail_quote">2010/2/23 Julian Bäume <span dir="ltr"><<a href="mailto:julian@svg4all.de">julian@svg4all.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Saturday 20 February 2010 20:49:11 P Zoltan wrote:<br>
> The next thing i wanted to do is to merge the testing code in the kde4<br>
> port tree. I have to learn more abot git to know how to do it; if anyone<br>
> wants to do this, I'd happily copy the merged tree, and work on that.<br>
</div>done that. I also removed the Eigen sources and added everything to the<br>
CMakeLists.txt that is necessary to find the eigen headers. This was a little<br>
more git work, than just merging, since I also did a rebase, so the Eigen<br>
sources even don't show up in the history.<br></blockquote><div></div><div><br> Those junk-related commits could be also deleted (by mistake i've<br>comitted the build binaries in the repository, then deleted it).<br>
<br> Here is a problem: if cmake can't find eigen2, it still tries to build<br>the tests, and fails. So a minor issue will turn to a build faliure. The<br>tests should be only built when eigen2 is found.<br><br><br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I also moved around your files a bit. You can find your test in tests/math.<br>
For now, there seems to be no output (at least for me), I'm not sure, what has<br>
to be done to get it back. </blockquote><div></div><div></div><div><br> Here is a useful blog entry on this:<br><br><a href="http://ktutorial.wordpress.com/2009/03/18/unit-testing-a-kde-4-library/">http://ktutorial.wordpress.com/2009/03/18/unit-testing-a-kde-4-library/</a><br>
<br> So in the build directory, you need to run "ctest" to run the tests, and<br>"ctest -V" or "ctest -VV" to see all the output. This verbose mode should<br>be somehow integrated in the cmake files.<br>
<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">To run the test, build the sources (run cmake and<br>
make) and then run "make test". If you don't have latest KDevPlatform beta8,<br>
you need to revert the commit I mentioned in one of my last mails or merge the<br>
_prebeta8 branch. If you are not sure, just try to compile, cmake will<br>
complain, if KDevPlatform is to old.<br>
<br>
Another thing, I want to mention is a blog post of one of the kdevelop hackers<br>
about unittests for kdevelop plugins.<br>
<a href="http://apaku.wordpress.com/2010/02/17/writing-unittests-for-kdevelop-plugins/" target="_blank">http://apaku.wordpress.com/2010/02/17/writing-unittests-for-kdevelop-plugins/</a><br>
<br>
This should help us implementing tests like the project management stuff, I<br>
started to port to KDevPlatform interfaces. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
bye then<br>
<font color="#888888">julian<br>
</font><br>------------------------------------------------------------------------------<br>
Download Intel® Parallel Studio Eval<br>
Try the new software tools for yourself. Speed compiling, find bugs<br>
proactively, and fine-tune applications for parallel performance.<br>
See why Intel Parallel Studio got high marks during beta.<br>
<a href="http://p.sf.net/sfu/intel-sw-dev" target="_blank">http://p.sf.net/sfu/intel-sw-dev</a><br>_______________________________________________<br>
Ktechlab-devel mailing list<br>
<a href="mailto:Ktechlab-devel@lists.sourceforge.net">Ktechlab-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/ktechlab-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/ktechlab-devel</a><br>
<br></blockquote></div><br>