Skip to content

Conversation

@vszakats
Copy link
Member

@vszakats vszakats commented Feb 6, 2025

As detected using cmake --warn-uninitialized.

It also lists:

https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-warn-uninitialized

As detected using `cmake --warn-uninitialized`.

It also lists variables inherited from `Makefile.inc`, which this PR
does not fix. And also three envs: `CI`, `CURL_CI` and `CURL_BUILDINFO`.
That's unexpected:
https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-warn-uninitialized
and as of August 2024, there is no solution to silence:
https://discourse.cmake.org/t/how-to-test-for-set-env-variables-without-getting-warnings/11401
@testclutch

This comment was marked as outdated.

@vszakats vszakats closed this in aa3e4c1 Feb 6, 2025
@vszakats vszakats deleted the cm-uninit branch February 6, 2025 22:33
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
As detected using `cmake --warn-uninitialized`.

It also lists:
- variables inherited from `Makefile.inc`, which this PR does not fix.

- a documented CMake global variable, which is unexpected:
  `CMAKE_MODULE_PATH`.
  I'd expect CMake to initialize its namespace.

- envs: `CI`, `CURL_CI` and `CURL_BUILDINFO`. Unexpected, as the manual
  mentions variables only. As of August 2024, there is no solution to
  silence them:
  https://discourse.cmake.org/t/how-to-test-for-set-env-variables-without-getting-warnings/11401

https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-warn-uninitialized

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

Development

Successfully merging this pull request may close these issues.

2 participants