mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-03 20:29:56 -06:00
01d7860fdb
Since * commiteed295fd8a(cmGlobalNinjaGenerator: require that dependency info files work, 2023-02-01, v3.26.0-rc1~1^2~1), and * commit13810dee17(cmDependsFortran: require that dependency info files work, 2023-02-01, v3.26.0-rc1~1^2), the Ninja and Makefile generators' module dependency scanning requires that scanning results from from linked targets is available before scanning the current target. In the case of a static library cycle, we cannot expect this information from other static libraries in the cycle. Previously we supported cyclic cases at the cost of silently ignoring missing information. We already compute a global order of targets that respects all `add_dependencies`, but may break `target_link_libraries` dependencies that occur in a static library cycle. Use this order to filter the linked targets so we only expect scanning results to be available from those targets that build before the current target. This approach is sufficient to support module dependency scanning in static library cycles as long as module dependencies do not cross between two libraries in the same cycle. Fixes: #24631
17 lines
539 B
CMake
17 lines
539 B
CMake
include_directories(${Library_MODDIR})
|
|
add_library(subdir_mods a.f90 b.f90)
|
|
add_executable(subdir_exe main.f90)
|
|
target_link_libraries(subdir_exe subdir_mods)
|
|
|
|
add_library(cycleA STATIC cycleA1.f90 cycleA2.f90)
|
|
add_library(cycleB STATIC cycleB1.f90 cycleB2.f90)
|
|
target_link_libraries(cycleA PRIVATE cycleB)
|
|
target_link_libraries(cycleB PRIVATE cycleA)
|
|
|
|
# Test module output directory if available.
|
|
if(CMAKE_Fortran_MODDIR_FLAG)
|
|
set_target_properties(subdir_mods cycleA cycleB PROPERTIES
|
|
Fortran_MODULE_DIRECTORY modules
|
|
)
|
|
endif()
|