On Wednesday 29 June 2011, Pavel Heimlich, a.k.a. hajma wrote: > 2011/6/29 Allen Winter <[email protected]>: > > Howdy, > > > > I copied the current kdelibs/cmake into extra-cmake-modules. > > History should be retained. > > > > So now we need to start hacking away. > > Hi, > is there an easy way to mass-test all the modules? > I imagine I would run them all on my KDE build machine and I would > only quickly wade through the output of what they detected to see if > it's as expected.
That's hard, because in order to properly test whether a FindFoo.cmake works, you would have to know whether Foo is installed, and where, automatically, to be able to compare the result with what you expect. What is done in cmake is to have a test which at least include()s all FindFoo.cmake files, so all are at least executed, so they contain at least valid code. The results are not checked. Not sure how this can be improved... Alex _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
