naveen-seth wrote: > [cmake.log.tar.gz](https://github.com/user-attachments/files/23736926/cmake.log.tar.gz) > > ``` > $ cmake --version > cmake version 4.2.0 > > CMake suite maintained and supported by Kitware (kitware.com/cmake). > > $ ninja --version > 1.13.2 > ```
With `set_property(GLOBAL PROPERTY GLOBAL_DEPENDS_NO_CYCLES ON)`, CMake will analyze the full dependency graph at the beginning and report an error if the global target dependency graph contains a cycle (even for static libraries). The CMake logs you have attached show that no cycle was detected and the configuration step runs without error. (To confirm this, I also tested configurations where I intentionally introduced direct and transitive cycles, and CMake correctly failed with an error during the configuration step in those cases.) >``` > $ ninja > ninja: error: dependency cycle: lib/libclangDriver.so.22.0git -> > lib/libclangFrontend.so.22.0git -> lib/libclangDriver.so.22.0git > ``` Is this the output from running ninja in for the build which generated the logs you have attached? If your build still fails, can you attach your `deps.dot.clangFrontend`, `deps.dot.clangFrontend.dependers`, `deps.dot.clangDriver`, `deps.dot.clangDriver.dependers` after adding `--graphviz=<path-to-output-graphviz>/deps.dot` to your CMake command? https://github.com/llvm/llvm-project/pull/169397 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
