Dmitry, Alternatively, rather than changing the Directories under Visual Studio settings - which is a global change, I tried by setting the appropriate environment variables in tools.ini for the Localization project.
So, for instance, I set the $PATH=$(PATH);my_xerces_exe_dir Similarly, $LIB, and $INCLUDE variables. However, the "move" command still fails - so for now, I manually moved the files, and commented out the "move" in the .mak file to build Localization. If you can come up with any ideas to make the move work, please let me know! Thanks, Urmi -----Original Message----- From: Chatterjee, Urmi Sent: Thursday, April 08, 2004 9:42 AM To: [email protected] Subject: RE: Compiling Xalan 1.7 with .NET 2003 Dmitry, I'm working on Windows 2000 Server. And I am trying with both VC 6.0 as well as .NET 2003 - both should work if one works. For now, I could manually copy the generated files, and then comment out the "move" command that fails in Localization.mak, to see if I can proceed further. But other groups and developers will be using the same source, and for them to be able to build smoothly I will need to ensure these problems are resolved. Thanks, Urmi -----Original Message----- From: Dmitry Hayes [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 8:23 PM To: [email protected] Subject: RE: Compiling Xalan 1.7 with .NET 2003 Hi again! In xml-xalan\c\Projects\Win32\VC6\Utils\Localization\Localization.mak , line 78 you could see two basic "move" commands , moving created by MsgCreator hpp files from directory to directory . What's your Win version ? Thanks! Dmitry "Chatterjee, Urmi" <Urmi.Chatterjee@ To ca.com> <[email protected]> cc 04/07/2004 01:56 PM Subject RE: Compiling Xalan 1.7 with .NET 2003 Please respond to xalan-c-users Thanks for the hint, Dmitry! I got further with your help, but now the compilation fails in the last stage, I think. It looks like I probably should put quotes around something, to handle this, but can't figure out where. This is the error I get: Used BITS = Win32 Used CFG = Debug Used LOCALE = en_US Used TYPE = inmem Used XLIFF file: "XalanMsg_en_US.xlf" ..\..\..\..\..\Build\Win32\VC6\Debug\MsgCreator.exe ..\..\..\..\..\src\xalanc\NLS\en_US\XalanMsg_en_US.xlf -TYPE inmem -LOCALE en_US The filename or extension is too long. NMAKE : fatal error U1077: 'move' : return code '0x1' Stop. Error executing nmake. Localization - 1 error(s), 0 warning(s) The header files have been generated, but looks like the move fails. Thanks again for your help! Urmi -----Original Message----- From: Dmitry Hayes [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:32 PM To: [email protected] Subject: RE: Compiling Xalan 1.7 with .NET 2003 Hi ! Have you tried to put Xerces in Tools->Options->Projects->VC++ Directories , in "Executable file","Include files" and "Libarary files" ? A documentation how to build with .NET will be ready for Xalan1.8 release , but the same idea like for VC6 should work . Thanks, Dmitry "Chatterjee, Urmi" <Urmi.Chatterjee@ To ca.com> <[email protected]> cc 04/07/2004 11:44 AM Subject RE: Compiling Xalan 1.7 with .NET 2003 Please respond to xalan-c-users Hi Matt, Thanks for your response. I checked the instructions on how to rebuild Xalan on the web link you mentioned. I see the AllInOne dependency on Localization. When I try to build to build Localization - it fails as it is unable to find Xerces header files. But I did update the Xerces include path, in the AllInOne.dsp to the correct location. I am not sure, if that is the only dsp file I need to update - I could not find a way to specify the Xerces paths in the Localization project. Thanks, Urmi -----Original Message----- From: Matthew Hoyt [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 5:01 PM To: [email protected] Subject: RE: Compiling Xalan 1.7 with .NET 2003 Hi Urmi, How are you building Xalan with Visual Studio 6? The file you are looking for is generated during compile time. This is part of the message localization feature. For Visual Studio 6, if you load up the Xalan.dsw workspace and build the AllInOne project or any of Xalan executables that depend on it , the header file will be created at the start of the build process (it is generated by Localization project, which AllInOne project depends on). See http://xml.apache.org/xalan-c/readme.html#win32 for build instructions. -Matt. "Chatterjee, Urmi" <Urmi.Chatterjee@ To ca.com> <[email protected]> cc 04/02/2004 04:38 PM Subject RE: Compiling Xalan 1.7 with .NET 2003 Please respond to xalan-c-users Hi, I am facing the same problem when I build Xalan 1.7 on VC 6.0. Has anyone else faced this problem before? I could not locate the file it is asking for. Thanks in advance, Urmi From: Chatterjee, Urmi Sent: Friday, April 02, 2004 11:32 AM To: [email protected] Subject: Compiling Xalan 1.7 with .NET 2003 Hi, I am trying to compile Xalan 1.7 on .NET 2003. I have a couple of questions: 1. Is Xerces 2.5 the right version to use? 2. I am getting compilation errors as follows: ..\..\..\..\src\xalanc\PlatformSupport\XalanMessageLoader.hpp(67) : fatal error C1083: Cannot open include file: 'LocalMsgIndex.hpp': No such file or directory I have not been able to locate the specified file. Until now, I had been using Xalan 1.6 with Xerces 2.3 and compiling on VC 6.0, and the default project options worked without me making any changes. Are there any changes I need to make to the project in this case? Any help would be welcome! Thanks, Urmi
