Hi Unri !
The tools.ini file used to collect macros setting for VC++ makefiles , and
it can be called from any makefile.
In our implementation only a makefile in the same directory reads it.
But the problem is different: we are building Xalan with dsp/dsw (or
vcproj/sln) and not with exported makefiles.
I'm not sure that dsp/dsw files inherit environmental variables values ,
like makefiles do .
At least , I haven't found a documentation in MSDN describing that.
Thanks,
Dmitry
"Chatterjee,
Urmi"
<Urmi.Chatterjee@ To
ca.com> <[email protected]>
cc
04/08/2004 04:08
PM Subject
RE: Compiling Xalan 1.7 with .NET
2003
Please respond to
xalan-c-users
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
