Niels Lohmann

I like the idea, but the current approach is mixing a lot of things: downloading, keeping a version list, and the actual checks. I am currently not entirely sure if...

After deleting CMake 3.9.3, it works again: ``` ./cmake_min_version.py ~/Downloads/cmake_min_test1/ Found 129 CMake binaries from directory tools [ 0%] CMake 3.13.0 ✔ works [ 12%] CMake 3.5.0 ✘ error [...

Interesting: ``` [ 83%] CMake 3.8.2 ✔ works [ 83%] CMake 3.9.0 ✘ error [ 83%] CMake 3.9.1 ✔ works [ 84%] CMake 3.9.2 ✘ error [ 84%] CMake 3.9.3...

More output: ``` [ 83%] CMake 3.8.2 ✔ works [ 83%] CMake 3.9.0 ✘ error Boost found. Found Boost components: system;thread CMake Error in /Users/niels/Code/repositories/cmake_min_version/tools/cmake-3.9.0-Darwin-x86_64/CMake.app/Contents/share/cmake-3.9/Modules/FindBoost.cmake: cmake_policy PUSH without matching POP...

I leave this open as concept bug - the binary search assumes monotonous behavior; that is, if a project can be built by version x, then it should also be...

With #26, I changed the behavior of the full search to return the latest version such that this and all later version can successfully build the project.

There are different problems now: ``` [ 0%] CMake 3.16.1 ✔ works [ 11%] CMake 3.8.2 ✘ error CMake Error at CMakeLists.txt:8 (message): CMAKE_PROJECT_VERSION is not defined [ 22%] CMake...

I will check locally. Maybe we need an option to dump the actual error message for each version.

I tried the project locally using macOS. I first had an error with all CMake versions, because Boost was not installed. Once I fixed that (`brew install boost`), I got...

I now added an `--error_details` flag. With it, you can display the stderr output which could help identifying the reason why CMake failed.