[Dune-devel] 'make test' vs. 'ctest'

Christoph GrĂ¼ninger foss at grueninger.de
Sat Aug 11 01:02:45 CEST 2018


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Oliver,
'ctest' is a tool provided by the CMake makers to offer a simple
command line tool for test execution. To have serious testing a proper
tool like CDash, Jenkins, or what we have integrated in our GitLab.
'make test' is a poor wrapper to call ctest. It might be handy and if
you seldom touch CMake it might be convenient to stay within the world
of your build tool.
So in doubt use ctest.

This is all a matter of CMake and no decision from Dune. If our
documentation states otherwise, we should update it. It was written
under the impression of helping people to switch from Autotools.

Bye
Christoph


Am 10.08.2018 um 16:37 schrieb Oliver Sander:
> Dear Dune,
> 
> I am trying to understand the build system a little better, and I
> have just learned from looking at the code that the 'make test'
> target is really nothing more than a call to 'ctest' (with one
> argument the necessity of which is not clear to me).  What is the
> reason for having 'make test'?  Why not expect people to call
> 'ctest' directly like for other cmake projects?
> 
> Thanks, Oliver
> 
> 
> 
> _______________________________________________ Dune-devel mailing
> list Dune-devel at lists.dune-project.org 
> https://lists.dune-project.org/mailman/listinfo/dune-devel
> 

- -- 
Unfortunately, plots are notoriously hard to get right. Partly, the
default settings of programs like gnuplot or Excel are to blame for
this since these programs make it very convenient to create bad plots.
                        -- Till Tantau, "The TikZ and PGF Packages"
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE7sBEdTkOnKktLWzhxpBF3qbro8kFAltuGZAACgkQxpBF3qbr
o8mW5Q//XXvviS5NLmFsvDR/qXDsOUylFhj0lQdD+IM7VP5DpQxDXxKOaAuLRSSL
FsjEXOj9Nm0inK7MKT82C62BhiscksZCuPKwR4gPvBKvN8vOLBsrp8JOGVaWHXfc
bHpchqabijxlNHddQcX+FEFFJaCwjw2lvV0AwzNfDQLcBVmTu40UxEgyL1MTMfzf
XD/W3HXhFqRHKBlqLF4gWa9dL4t8L0MkscJ+wrn4/Qx3TeZz4nvvtGGq7+ZYHFkE
2Q72GPOs9YpLblGyVKOSJC7OOoAUJMyTujmWMWb1dc1BoTfsBkAZ+2iMS8EWtJ2L
ylJE8xdQqiXJ6kggRkdPXIW/i4s62bFur3lVzi4vbUTA8FRE4Y9ZiZ5Ud51V64BX
uxc+S8UJB5qu2n2ibVxTny1v0U9/60SwNAlHgVXTAOUSx2OF7kGc7HwmtuBSqVpd
iTd/qo9VRQ2VQMSg2wS16G4vxw7bQmhDy93VI45OjghQnYkirIQEsQ0ccaGYNLky
BnS8f0ErWSfCO+NzMJF5pTpxIEq08JlCPFtSJRiv4D0OJgzqaxc6IC/mdybz8eBC
CDosuN0j86U3/UXxyKXFHy3WASXQvJ1yGQL9wJtfslxCmRTuf8OHe9BkV+vyMnMi
7PHZZBt+SsX+ZDmrOeAZjMlU5lEWn4pjvOiGmFucWaQhg6h70f4=
=xWev
-----END PGP SIGNATURE-----




More information about the Dune-devel mailing list