Ok thanks. But it is unfortunate, since it means that really great macros, such as project_guarded (see http://stackoverflow.com/a/33100078) cannot be used everywhere, as a substitute for project.
On Tue, Apr 26, 2016 at 8:04 PM, Chuck Atkins <chuck.atk...@kitware.com> wrote: > ajneu, > > The call to project(...) needs to be explicit. See > https://cmake.org/cmake/help/v3.5/command/project.html: > > The top-level CMakeLists.txt file for a project must contain a literal, > direct call to the project() > <https://cmake.org/cmake/help/v3.5/command/project.html#command:project> > command; loading one through the include() > <https://cmake.org/cmake/help/v3.5/command/include.html#command:include> > command is not sufficient. > > - Chuck > > On Tue, Apr 26, 2016 at 1:57 PM, aj neu <ajn...@gmail.com> wrote: > >> Hi, >> >> when calling `project` >> ...as seen here >> ... >> https://github.com/ajneu/cmake_project_via_macro/blob/5972c7362e11fdbaa09d9defe8cca2dcea79e606/CMakeLists.txt#L33 >> everything is ok. >> >> >> BUT when calling `project` via a macro (that was included) >> ... as seen here >> ... >> https://github.com/ajneu/cmake_project_via_macro/blob/master/CMakeLists.txt#L33 >> the behaviour is not as expected. >> >> Why? >> >> (Details are here: https://github.com/ajneu/cmake_project_via_macro) >> >> >> Is this a bug? >> >> Thanks >> ajneu >> >> >>
-- 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: http://public.kitware.com/mailman/listinfo/cmake
