Re: [CMake] project command not working, when used via macro (from an included file)

Perhaps I spoke to hastily. It seems the unsupported configuration is if project(...) is actually called from an include file, which makes sense given various scoping issues. Give that, what you have should work fine. What doesn't work as expected? It seems to work just fine when I try it from

Re: [CMake] project command not working, when used via macro (from an included file)

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 wrote: > ajneu, > > The

Re: [CMake] project command not working, when used via macro (from an included file)

at 20:04 To: aj neu <ajn...@gmail.com<mailto:ajn...@gmail.com>> Cc: "cmake@cmake.org<mailto:cmake@cmake.org>" <cmake@cmake.org<mailto:cmake@cmake.org>> Subject: Re: [CMake] project command not working, when used via macro (from an included file) ajneu, The ca

Re: [CMake] project command not working, when used via macro (from an included file)

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()

[CMake] project command not working, when used via macro (from an included file)

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 ...