Well, in my real case this happens even with out-of-source builds, which
also occurs in the test case if I change:
set (OUT ${CMAKE_BINARY_DIR}/ext)
in ext/CMakeLists.txt.
Sure, I can avoid it by renaming the file or target, but I thought this
is something that could be avoided by either (a)
Hi,
This is caused by doing an in source build and thereby causing the issue.
The custom command is outputting a file called 'foo', which is also the
chosen name of a target in the ninja file. All of this results in ninja
conflating the two and causing a circular dependency.
Your options are to
Hello,
I have a project where circular dependencies are generated when I use
the Ninja generator, but not the default Unix Makefiles. I could create
a minimal test like this:
$ cat CMakeLists.txt
add_subdirectory (ext ${PROJECT_BINARY_DIR}/ext)
$ cat ext/CMakeLists.txt
set (OUT
