You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatically run unit tests (we need to select a unit test framework for c++), possible with a memory checker on
The idea is that CMake should set up the whole 3rdparty environment itself, such that end-users should not install anything in order to make our code work and run. Just run CMake on our stuff and then build our things philosophy.
Regarding unit tests, we have in the past used the Boost unit test framework. It works really well, but it is a huge dependency to have for only using the unit test framework and further, it needs a binary install which makes it a little inconvenient too. Many of the other dependencies will work as header-only libraries which greatly simplify dealing with 3rd party libraries. Hence, it might be worthwhile to study other options for unit test frameworks in C++ before deciding on our final choice for libRAINBOW.
Our C++ code standards are heavily influenced by the OpenTissue project
Integrate CMake into GitHub workflows such that C++ code gets compiled and C++ unit tests run when trying to do a pull request on the main branch.
Here is a bit of getting started boilerplate code
https://github.com/marketplace/actions/run-cmake
Here is a checklist of features we need
The idea is that CMake should set up the whole 3rdparty environment itself, such that end-users should not install anything in order to make our code work and run. Just run CMake on our stuff and then build our things philosophy.
Regarding unit tests, we have in the past used the Boost unit test framework. It works really well, but it is a huge dependency to have for only using the unit test framework and further, it needs a binary install which makes it a little inconvenient too. Many of the other dependencies will work as header-only libraries which greatly simplify dealing with 3rd party libraries. Hence, it might be worthwhile to study other options for unit test frameworks in C++ before deciding on our final choice for libRAINBOW.
Our C++ code standards are heavily influenced by the OpenTissue project
https://github.com/erleben/OpenTissue
We have made several "descendants" from OpenTissue such as
https://github.com/diku-dk/PROX
These illustrate well how we wish to write C++ code to be included in libRAINBOW.
The text was updated successfully, but these errors were encountered: