> Am 24.12.2018 um 17:07 schrieb Kyle Edwards <kyle.edwa...@kitware.com>: > > On Sat, 2018-12-22 at 16:57 +0100, Torsten Robitzki wrote: >> What I’m still missing is support to define dependencies between >> different targets (build by different toolchains), so that I can >> describe that I require a tool that is build with the HostToolChain, >> to generate a file that is required by the part of the build, that is >> using the CrossToolChain. And, of cause, if the source of that tool >> changes, that tool have to be rebuild and the generated file from the >> CrossToolChain part of the build have to be rebuild. > > What about add_dependencies()? Is that sufficient, or is there > something more that you need?
If it would be possible to use add_dependencies() to describe dependencies between two targets build with two different toolchains, then this would be sufficient: add_dependencies(signed_firmware TOOLCHAINS CrossToolChainA CrossToolChainB firmware_signing_tool TOOLCHAIN HostToolChain) best regards, Torsten -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
