There is no question that this should be handled automatically, but that
requires somebody pre-process the source files and generate additional
dependencies. It would nice if the compiler took care of that, or we would
need to parse the source files in some task, collect the new dependencies,
and use them in the cl task. Not exactly clean, but if someone wanted to do
it, I'm sure a patch would be considered. I'm no expert on C++ dependencies,
but I'm sure there are some other issues in there too. This doesn't sound
like a trivial exercise.

In VB and C# the other dependencies are libraries and resources primarily.
As these are referenced in the tasks that compile the source files, it is
easy to check if they have been updated. This makes it much easier to do the
right thing.

----- Original Message ----- 
From: "Castro, Edwin Gabriel (Firing Systems Engr.)" <[EMAIL PROTECTED]>
> The only downside to this method is that you need to know the
> dependencies ahead of time and manually put them in the build file. One
> would think that a utility to do this for you would exist...
>
> Then again, most people using .NET technologies are using VB or C#.
> Unfortunately, this means that people using C++ are left behind because
> our issues are left on the back burner.



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to