Hi Don, The approach I suggested takes care of that problem specifically, since the environment variables are set in the tools.ini specific to the project, in this case, it is Localization. They are active only when Localization is built.
It is also the method recommended in the MSDN library - NMAKE reference. Hope that helps! Thanks, Urmi -----Original Message----- From: Don McClimans [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 2:48 PM To: [email protected] Subject: Re: Compiling Xalan 1.7 with .NET 2003 Dmitry Hayes wrote: > You are correct, there are more then one way to specify > include/lib/executable setting ... Off the main topic of this thread, but I strongly urge you to dispense with the idea of changing the global paths in VC++. This is a pain for those of us who cannot have xerces in our include and lib paths for other projects. A global environment variable such as $INCLUDE suffers from similar problems. A better solution, in my opinion, is to use a specific environment variable (eg, XERCESINCLUDEPATH) and use that variable name in the the project (dsp) file. This only requires that users add a couple of environment variables, which is no more difficult than changing the VC global directories, but is less invasive. Also, you can then use the same approach in windows and *nix builds. Don
