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 <felix.ram...@kuka.com> wrote: > > 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 file) don’t appear again. > > Is this the standard behavior? > > > > Thanks, > > Felix > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
