Am Donnerstag, 21. Februar 2013 um 09:45:16, schrieb Scott Kostyshak <skost...@lyx.org> > > In the case of knitr, it's probably better to do something like > checking the exit code of the following command: > R -e "library(knitr)" > Ideally, we would also check > R -e "packageVersion(\"knitr\")" > To make sure it is recent enough.
Good idea.
> >> Another possibility is that it's up to the users which tests they
> >
> >> should run. For example, I could have local .ctestignore where I list
> >
> >> the
> >
> >> tests for which I don't meet the dependencies. ctest -R would not run
> >
> >> the tests listed in .ctestignore.
> >
> >
> >
> > Where should the ".ctestignore" be? Why not have the info directly in
> > CMakeLists.txt?
>
> This was for if it was up to the users to decide which tests they
> ignored. I would make .ctestignore and you would have your own one.
> Ours would be different because we have different dependencies
> installed. Of course, if CMakeLists.txt can do everything
> automatically as we're discussing above, that would be nice.
Ctest does not care, so we have to do it at config time to get
it into the ctest files. It looks more natural to me, to do it the cmake way.
To ignore a test like knitr I would call
#ctest -R export/examples -E knitr -E sweave
As long as cmake can get things automatically, it should do so.
> Scott
Kornel
signature.asc
Description: This is a digitally signed message part.
