Feature idea
Currently there is no trivial way to check the sanity of an installation of t8code.
Checking that is currently a manual task.
As such, it may cost time to detect: more to a new user, perhaps less to t8code developers.
A post-installation testing procedure, no matter how minimal, could catch some installation problems early.
One may install minimal Makefiles, CMakeLists.txt and/or scripts first, and complement that with a thin make post_install_tests target invoking that.
These files, pre-installed in the directories where documentation lays, would also help the user to write own t8code-based programs -- which helps the adoption of t8code.
About alternatives:
Documentation mentioning how to build a test program is surely useful.
But it does not replace a readily usable post-installation procedure provided by the developers, perhaps turning on/off features as to reflect the build-time configuration of the library.
The feature request has little priority.
It clusters thematically to #2225 .
Feature idea
Currently there is no trivial way to check the sanity of an installation of t8code.
Checking that is currently a manual task.
As such, it may cost time to detect: more to a new user, perhaps less to t8code developers.
A post-installation testing procedure, no matter how minimal, could catch some installation problems early.
One may install minimal
Makefiles,CMakeLists.txtand/or scripts first, and complement that with a thinmake post_install_teststarget invoking that.These files, pre-installed in the directories where documentation lays, would also help the user to write own
t8code-based programs -- which helps the adoption oft8code.About alternatives:
Documentation mentioning how to build a test program is surely useful.
But it does not replace a readily usable post-installation procedure provided by the developers, perhaps turning on/off features as to reflect the build-time configuration of the library.
The feature request has little priority.
It clusters thematically to #2225 .