On 06/29/2010 08:40 AM, Tom Birch wrote:
On Jun 28, 2010, at 10:09 AM, Michael Hertling wrote:
On 06/28/2010 05:24 AM, Tom Birch wrote:
CMake's dependency scanner uses its own parser to scan for #include
directives, and then builds up the dependency tree this way. I know it's
possible
On Jun 28, 2010, at 10:09 AM, Michael Hertling wrote:
On 06/28/2010 05:24 AM, Tom Birch wrote:
CMake's dependency scanner uses its own parser to scan for #include
directives, and then builds up the dependency tree this way. I know it's
possible to rig up an invocation of gcc -M to generate
On 06/28/2010 05:24 AM, Tom Birch wrote:
CMake's dependency scanner uses its own parser to scan for #include
directives, and then builds up the dependency tree this way. I know it's
possible to rig up an invocation of gcc -M to generate the correct
dependencies, and then feed this into the
CMake's dependency scanner uses its own parser to scan for #include directives,
and then builds up the dependency tree this way. I know it's possible to rig up
an invocation of gcc -M to generate the correct dependencies, and then feed
this into the OBJECT_DEPENDS property of source files, but
