Dear David, Hey, it worked!
Just one problem: it's looking for httpd.h for Configuration: ApacheModuleXSLT. I searched and found two different versions - one in cygwin\usr\include\apache, the other in cygwin\usr\include\apache2. Their dates and file sizes are different (45k vs 62k). Which one should I use? - Phil PS - Two tips to all who find this entry after googling/looking in the mail archives: 1) Edit the you-know-what out of the tools.ini file - if there's a directory that needs to be in PATH, LIB, or INCLUDE, put it in there. (e.g. PATH=C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;$(PATH) )Directories holding DLL's need to be in PATH and maybe in LIB too. The Windows with ICU build is a completely different ballgame from any of the Unix builds. 2) If you are only building with 32-bit libraries, make sure to go into Build/Batch Build and uncheck the 64-bit entries. Otherwise, it's gonna have problems finding the 64-bit version of LocalMsgIndex.hpp . -----Original Message----- From: David Bertoni [mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006 8:26 PM To: xalan-c-users@xml.apache.org Subject: Re: NT build, LocalMsgIndex.hpp error, FAQ and googling NOT helping Schlesinger, Philip wrote: > Hi all. Building on NT with Visual C++ 6. Getting the following > error during build: > > <snip> > PlatformSupportInit.cpp > C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(39) : > warning C4100: '_P' : unreferenced formal parameter C:\Program > Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(41) : > warning C4100: '_P' : unreferenced formal parameter > C:\bldtogether\xml-xalan\c\src\xalanc\PlatformSupport\XalanMessageLoad > er > .hpp(29) : fatal error C1083: Cannot open include file: > 'LocalMsgIndex.hpp': No such file or directory </snip> > > I've read the FAQ. I've tried the rules listed in build_instruct.html > for building on Windows with ICU and tried what they told me. I > googled and found tips in the message archives for this group. Still > getting this error. > > I've read through the build messages and it seems almost as if > LocalMsgIndex.hpp isn't even being built - the first reference to it > is the error message above on line 163. I uploaded the build messages > and the tools.ini to: > > http://www.electronicfiles.net/files/3560/20060710%20nt%20xalan%20buil > d% > 20problems.ZIP > > HELP?! It sounds to me like you haven't put the Xerces-C library on your path. Look in the build output window to see if there are any error messages. If the MsgCreator executable doesn't run, it won't create LocalMsgIndex.hpp, and the build will fail. You might also try a clean build by deleting the Build directory. An alternative to putting the Xerces-C executables on the path is to place them in the corresponding Debug and Release build directories: Build\Win64\VC6\Debug\ Build\Win64\VC6\Release\ Dave
