Thanks , Don , I'll try it .
Dmitry
Don McClimans
<[EMAIL PROTECTED]
lectronics.com> To
[email protected]
04/08/2004 05:14 cc
PM
Subject
Re: Compiling Xalan 1.7 with .NET
Please respond to 2003
xalan-c-users
Dmitry Hayes wrote:
> 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 .
Yes, they do. At least, if by "inherit" you mean inherit from the system
environment. I use this all the time. The syntax is slightly different,
though.
For example, in the project settings, C/C++, Preprocessor, you would add an
entry "$(XercesIncludePath)". Assuming you have an environment variable
XercesIncludePath, this would add that path to the include search list.
Alternatively, you could put "$(XercesPath)/include" into the include list,
and "$(XercesPath)/lib" into the library list.
Don
- RE: Compiling Xalan 1.7 with .NET 2003 Dmitry Hayes
- RE: Compiling Xalan 1.7 with .NET 2003 Chatterjee, Urmi
- RE: Compiling Xalan 1.7 with .NET 2003 Chatterjee, Urmi
- RE: Compiling Xalan 1.7 with .NET 2003 Dmitry Hayes
- Re: Compiling Xalan 1.7 with .NET 2003 Don McClimans
- RE: Compiling Xalan 1.7 with .NET 2003 Chatterjee, Urmi
- Re: Compiling Xalan 1.7 with .NET 2003 Don McClimans
- RE: Compiling Xalan 1.7 with .NET 2003 Chatterjee, Urmi
- RE: Compiling Xalan 1.7 with .NET 2003 Dmitry Hayes
- Re: Compiling Xalan 1.7 with .NET 2003 Don McClimans
- Dmitry Hayes
