[nant-dev] Path dependencies for VisualCpp/some Win32 tasks

[Tharen D. Debold]

There are currently several tasks that require their “program” to be on the current path; is this the behavior that everyone uses/expects?   I’m referring to things like TLBImp, TLBExp, cl, Lib, Link, etc.   In our environment we have to change between compilers and such rather frequently, and so we prefer to not have these on our paths, but instead be in the build system (currently make) via properties/variables.   I’d like to do something to correct most of these NANT tasks; I have a few ideas, but I’m checking around for others.   To complicate life, some programs (notably CL) need more than one directory on the path; however they are related and might be able to be inferred if given a base path.  We might also want to use a base path (if supplied) to set the default value for include/lib directories in this scenario.   Ideally, there should be a way to default this for the current machine so that it did not have to be set for each compile.  I’d sure love to be able to build NANT and run the VisualCpp tests without having to muck with my environment each time…   Tharen