cmake: Fix build with GSSAPI - #3744
Conversation
|
The coverage decrease seems to be false. Only CMake files changed and the coverage build is done with the autotools... |
|
I suggest squash |
|
@jay If that's how you want to have it - no problem. I was just trying to make one thing per commit (if not for the clear history, then at least for review). |
|
@jzakrzewski you've just added more changes then required to solve #3743 :) |
|
Yeah, I've sneaked in some simple cleanup and my initial (but insufficient) solution using the |
Anything you want to leave separate please add |
|
Now it's hopefully nicer :) |
|
Yes it's better but I have some formatting suggestions for each:
|
- Remove nneeded include_regular_expression. It was setting what is already a default. - Remove duplicated include. - Don't check for pre-3.0.0 CMake version. We already require at least 3.0.0, so it's just clutter. Ref: curl#3744
With CMAKE_TRY_COMPILE_TARGET_TYPE set to STATIC_LIBRARY, the try_compile() (which is used by check_c_source_compiles()) will build static library instead of executable. This avoids linking additional libraries in and thus speeds up those checks a little. This commit also avoids curl#3743 (GSSAPI build errors) on itself with cmake 3.6 or above. That issue was fixed separately for all versions. Ref: curl#3744
|
Looking good. All the CI failures appear due to transient stalls and can be ignored. The coveralls 7% reduction in coverage doesn't make any sense to me. |
- Remove nneeded include_regular_expression. It was setting what is already a default. - Remove duplicated include. - Don't check for pre-3.0.0 CMake version. We already require at least 3.0.0, so it's just clutter. Ref: #3744
With CMAKE_TRY_COMPILE_TARGET_TYPE set to STATIC_LIBRARY, the try_compile() (which is used by check_c_source_compiles()) will build static library instead of executable. This avoids linking additional libraries in and thus speeds up those checks a little. This commit also avoids #3743 (GSSAPI build errors) on itself with cmake 3.6 or above. That issue was fixed separately for all versions. Ref: #3744
This primarily fixes #3743