; warning.
>
> -Ursprüngliche Nachricht-
> Von: Robert Maynard [mailto:robert.mayn...@kitware.com]
> Gesendet: Montag, 4. Februar 2019 18:16
> An: Ramold, Felix
> Cc: cmake@cmake.org
> Betreff: Re: [CMake] --warn-uninitialized works in only first configuration
>
ld, Felix
> Cc: cmake@cmake.org
> Betreff: Re: [CMake] --warn-uninitialized works in only first configuration
>
> This generally occurs with CACHE variables as for non first runs they
> exist in the cache and therefore are initialized.
>
> On Mon, Feb 4, 2019 at 10:16 AM R
list) also shows this warning.
-Ursprüngliche Nachricht-
Von: Robert Maynard [mailto:robert.mayn...@kitware.com]
Gesendet: Montag, 4. Februar 2019 18:16
An: Ramold, Felix
Cc: cmake@cmake.org
Betreff: Re: [CMake] --warn-uninitialized works in only first configuration
This generally occurs
This generally occurs with CACHE variables as for non first runs they
exist in the cache and therefore are initialized.
On Mon, Feb 4, 2019 at 10:16 AM Ramold, Felix wrote:
>
> Hi,
>
>
>
> I configure a project with --warn-uninitialized and get a lot of warnings. I
> successfully run the build.
Hi,
I configure a project with --warn-uninitialized and get a lot of warnings. I
successfully run the build.
Then I change any CMakeLists.txt file. I run the build again. CMake checks its
dependencies and reconfigures before the actual build.
Those warnings (or at least those in the edited
