Hi Don, I haven't worked that much with tools.ini either (in fact, this is my first experience!) - but it looks like it works with nmake - which can be invoked from the VC6 .dsp file or VC 7 vcproj file.
Yes, you are right, though - it does mean editing such an ini file for each such project. In such a situation, your suggestion would be a good way to do it. Thanks, Urmi -----Original Message----- From: Don McClimans [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 3:34 PM To: [email protected] Subject: Re: Compiling Xalan 1.7 with .NET 2003 Chatterjee, Urmi wrote: > 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. I haven't used tools.ini, but I thought that only worked for nmake, not for dsp files (at least in vc6?). I could be wrong, haven't tried it. If it does work for dsp files, wouldn't this mean you have to edit tools.ini for all the projects in the AllInOne workspace? I am concerned not with just making the localization project, but with specifying the location of the xerces include and lib paths for all the projects in AllInOne. Don
