You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 9, 2022. It is now read-only.
At present, a cmake script mystuff.cmake has to specify a dependency twice, once via include(dependency) and then again in DEPENDS ${dependency_NAME}. The second spec is easily forgotten, which can lead to bad behavior of a fresh buildem checkout. Unfortunately, the omission is not easily noticed by the developer of mystuff.cmake because dependency is usually already present in his build. Is it possible to remove the redundancy, e.g. by something like DEPENDS ${all_includes} which automatically makes all includes a dependency?
At present, a cmake script
mystuff.cmakehas to specify a dependency twice, once viainclude(dependency)and then again inDEPENDS ${dependency_NAME}. The second spec is easily forgotten, which can lead to bad behavior of a fresh buildem checkout. Unfortunately, the omission is not easily noticed by the developer ofmystuff.cmakebecausedependencyis usually already present in his build. Is it possible to remove the redundancy, e.g. by something likeDEPENDS ${all_includes}which automatically makes all includes a dependency?