New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Discussion] Versioning strategy #243

Open

bast opened this issue Apr 10, 2018 · 1 comment

Member

bast commented Apr 10, 2018

I would like to discuss and eventually solve a couple of issues:

Decide and clarify which CMake versions are supported and tested
It is not clear which modules are compatible with which CMake version
Autocmake has a global version but its semantics is not clear
If modules change should the global version change?
If not, how can we version the combination of framework and modules?

This also connects to #205 and #234.

bast mentioned this issue

refactor safeguards module #241

Merged

Member Author

bast commented Apr 10, 2018

Random thoughts:

I think that modules should carry CMake compatibility in their meta-info header and update script could check compatibility with the chosen min_cmake_version.
I don't think Autocmake should try hard to support CMake below 3.0.

bast mentioned this issue

omp module logic troubled by newer cmake #247

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment