Sorry, my earlier post was garbled.
Im in need of the CL task to understand C/C++
dependencies; i.e. #include, etc.
Ive got a simple dependency generator
that I can drop in, but Im wondering if this shouldnt be a
separate task; something similar to ANTs depend task.
(This way, you
Hello nant-developers,
I'm continuing my work on getting NAntAddin to run, and I need to
load the NAnt settings (framework configuration and so on) into the
project file created by the add-in. Previously, it was hard-coded that
the settings are loaded from the config file of the current
Tharen,
we definately care about the cl task. If you have some patches to offer
that you think would be applicable we would be very grateful.
Its not clear from your post what you mean by 'Im in need of the CL
task to understand C/C++ dependencies'. Could you please elaborate on this.
Ian
Currently, the CL task will recompile a file if and the source file
(.c/.cpp) is newer than the .obj file. If the .cpp file includes x.h,
and x.h is changed, nothing will be recompiled.
---
#include x.h
int main(int argc, char **argv)
{
// do something
return 1;
}
--
Unless I'm
I see what you mean. Essentially we need to re-invent visualc++'s
dependency checking stuff to determine what files shoudl and dhould not
be re-compiled.
Ian
Currently, the CL task will recompile a file if and the source file
(.c/.cpp) is newer than the .obj file. If the .cpp file includes
