Throw error when the compiler is not supported

[JackBoosY]

The current behavior will mislead the user into thinking that configuration was successful, when in fact it failed due to unsupported compiler version.

[JackBoosY]

Ref:
microsoft/vcpkg#40290
microsoft/vcpkg#40310
microsoft/vcpkg#39573
microsoft/vcpkg#39495
microsoft/vcpkg#38498

[klemens-morgenstern]

That's not a solution, that would break any cmake build on compilers that don't support C++20.
The configuration is fine as is, you can build boost, just without cobalt. This requires a fix on vcpkg.

[JackBoosY]

That's not a solution, that would break any cmake build on compilers that don't support C++20. The configuration is fine as is, you can build boost, just without cobalt. This requires a fix on vcpkg.

If I understand correctly, the configuration step will break when the compiler doesn't support cxx 20, isn't it?

[klemens-morgenstern]

Correct.

[JackBoosY]

Correct.

So I don't know why this changes is incorrect.
If the compiler doesn't meet the requirements, it should be FAILED at configure step, not just return and pass.

This affects not only vcpkg, but all steps using the command line, as they will collect the results of whether the configuration passed or not.

[klemens-morgenstern]

Because this is built as part of boost. Your change would make configuring boost fail if the compiler isn't supported.