>From: "Scott Hernandez" <[EMAIL PROTECTED]> >Sent: Wednesday, June 02, 2004 2:39 PM > 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
The compiler comes close to the usual UNIX/C/C++ way of solving this problem (at least for the VS.Net 2003 compiler): a. Use the /showIncludes option. b. Parse the results, which should be easy, and create a dependencies file from it. c. If the dependencies file doesn't already exist, then the compilation is presumed out of date and will be redone. If it does exist, then it's used to determine whether or not to recompile. In theory, this could be done via an explicit <include> task, or implicitly by the cl task. UNIX compilers typically output this information in a format all ready to be included in the makefile. It's a bit more work for NAnt to get the information into a suitable format, but it's certainly tractable. The /showIncludes output syntax is regular enough to make the parsing pretty easy. Gary ------------------------------------------------------- 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
