I guess what I am asking is - if I modified my build script to generate a text file (Makefile, CMakeLists.txt or whatever) containing the dependencies, would CMake be able to use it? I know that with GNU makefiles there is a way to generate additional makefiles as part of the build process (although it is rather complex and clumsy), I wonder if CMake can support something similar?<br>
<br><div class="gmail_quote">2009/12/30 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Wednesday 30 December 2009, Talin wrote:<br>
> What's the recommended way in CMake to do automated dependency generation<br>
> for languages that aren't directly supported by CMake? Suppose my compiler<br>
> generates an output file which contains a list of all the source files that<br>
> were used to make it, and I have some tool that can extract this<br>
> information. Is there some way I can get CMake to use this information in<br>
> subsequent builds?<br>
<br>
</div></div>The supported languages (C/C++, Fortran, somewhat Java and asm) have built-in<br>
C++ code for that in CMake (e.g. cmDependsC.cxx).<br>
I'm not aware of another possibility to do that.<br>
<br>
Alex<br>
</blockquote></div><br><br clear="all"><br>-- <br>-- Talin<br>