Bettina, Usually, the locale is specified on the build command line, which you can set from within Visual Studio. Click on Project->Settings for the Localization project, and for the specific configuration that you are building (eg Win32) go the "General" tab. The build command line should contain the TYPE and LOCAL settings. In any case, since you got past that point, your approach should work too.
I cannot come up with any ideas on why you are getting that error. One way you could debug is by adding an "echo $(LIB)" line to the Localization.mak file, so you can see what is the set of folders it is searching for the libraries. Urmi -----Original Message----- From: Bettina Reck [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 11:05 AM To: [email protected] Subject: RE: Compile error "Cannot open include file: 'LocalMsgIndex.hpp'" Hi, Urmi! Thanks again for your help! In the meantime, I partly had success. I had to specify the variable LOCALE to "en_US" in Tools.ini. But now I am sticking on the next error message: LINK : fatal error LNK1181: can't open input file "kernel32.lib" NMAKE : fatal error U1077: 'link.exe' : return-code '0x49d' Stop. NMAKE : fatal error U1077: 'if' : return-Code '0x2' Stop. Error in executing nmake. The global project settings to include kernel32.dll which can be found under the Visual Studio directory are correctly set. Any ideas? Bettina > Hi Bettina, > > Please check that the Locale is specified in the nmake command - I think > the default build command in the makefile is "nmake /f Localization.mak > TYPE=inmem LOCAL=en_US" for InMemory method (without ICU). You will probably > need to change the locale to the one appropriate to you. > > Please refer to the instructions on > http://xml.apache.org/xalan-c/readme.html#locale > for more details. > > Thanks, > Urmi > > -----Original Message----- > From: Bettina Reck [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 22, 2004 3:37 AM > To: [email protected] > Subject: RE: Compile error "Cannot open include file: 'LocalMsgIndex.hpp'" > > Hi, > > now I'm a step further on... At least I get another error message - the > one > and only (that's what you mentioned): > > Localization.mak(23) : fatal error U1050: Locale must be defined > Stop. > Error in excecuting nmake. > > Xalan-C_1_7_0.dll - 1 error, 0 warnings. > > Any ideas how to go on? > > Bettina > > > > > Bettina, > > > > I think the Xalan dependency on Localization is not set - if it were, > the > > first error/message you should see is when it tries to build > Localization. > > Go to Project->Dependencies. You should see Localization ticked under > the > > dependencies for AllInOne. > > > > If you set the Include/Lib/Exe paths using Tools->...etc that should > work > > for Localization, to look for the necessary files. > > > > Thanks, > > Urmi > > > > -----Original Message----- > > From: Bettina Reck [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 21, 2004 10:57 AM > > To: [email protected] > > Subject: RE: Compile error "Cannot open include file: > 'LocalMsgIndex.hpp'" > > > > Hi, > > > > I'm building Xalan form the .dsw - file, the error message still is > > > > > "F:\Reck\Xalan\xml-xalan\c\src\xalanc\PlatformSupport\XalanMessageLoader.hpp(67) > > : fatal error C1083: Include-file can't be opened: 'LocalMsgIndex.hpp': > No > > such file or directory" > > > > (I've translated part of the message as it was originally in German). > > > > Maybe there is still something wrong with the dependencies. You > mentioned > > "setting the Xerces path in AllInOne will not work for Localization...". > > How > > can I achieve to tell the Localization-project where to look for the > > necessary include-files? > > > > I'm using Win2000, is there anything else you might need to know? > > > > Thanks, > > Bettina > > > > > Hi Bettina, > > > > > > Could you tell me the exact error you are getting? > > > > > > Thanks, > > > Urmi > > > > > > -----Original Message----- > > > From: Bettina Reck [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, April 21, 2004 9:34 AM > > > To: [email protected] > > > Subject: RE: Compile error "Cannot open include file: > > 'LocalMsgIndex.hpp'" > > > > > > Hi, again! > > > > > > Thanks for the answers, but I'm still facing the same problem. I > > corrected > > > the project settings according to the documentation (put Xerces in > > > Tools->Options->Projects->Directories in "Executable file","Include > > files" > > > and "Libarary files"), I even set the build command line in > Localization > > > project and I verified the correct PATH-settings - still the same > > problem. > > > Any other ideas, what else could be wrong? > > > > > > Urmi, I am not sure how to handle the settings in the file Tools.ini - > > can > > > you give me some more information? > > > > > > By the way, is it correct to use the Xerces-binary-version or do I > need > > to > > > rebuild this again? > > > > > > Thanks, > > > Bettina > > > > > > > > > > Bettina, > > > > > > > > What are the errors you get while building Localization? > > > > > > > > In my case, the errors were resulting it not finding the Xerces exe, > > lib > > > > and include path. To fix that, I added the $LIB, $PATH, and $INCLUDE > > > macros > > > > in Tools.ini (in Localization folder) to append the appropriate > Xerces > > > path > > > > to the environment variable. For instance, > > > > > > > > LIB=$(LIB);$(XERCESROOT\build\$(BITS)\vc6\$(CFG) > > > > > > > > where XERCESROOT was a variable I defined for my relative Xerces > path. > > > > > > > > Similarly, for the other variables. > > > > > > > > Hope that helps. > > > > > > > > Thanks, > > > > Urmi > > > > P.S. Setting the Xerces path in AllInOne will not work for > > Localization, > > > > as it is built through a makefile using nmake. > > > > > > > > -----Original Message----- > > > > From: Bettina Reck [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, April 20, 2004 11:47 AM > > > > To: [email protected] > > > > Subject: RE: Compile error "Cannot open include file: > > > 'LocalMsgIndex.hpp'" > > > > > > > > Hi, Urmi! > > > > > > > > Thanks for your answer! I already red your mail and the answers and > I > > > > already tried to build Localization first but in fact in this > project > > > > there > > > > is nothing to build, only a file named XalanMsg_en_US.xlf. How do > you > > > > managed to build this project? > > > > (The dependencies are correctly set) > > > > > > > > Bettina > > > > > > > > > Hi Bettina, > > > > > > > > > > I had faced the same problem - the solution is to build > Localization > > > > > first. In fact, you should see the dependency on Localization in > the > > > > > AllInOne project. This would generate the required header files. > > > > > > > > > > Urmi > > > > > > > > > > -----Original Message----- > > > > > From: Bettina Reck [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, April 20, 2004 11:23 AM > > > > > To: [email protected] > > > > > Subject: Compile error "Cannot open include file: > > 'LocalMsgIndex.hpp'" > > > > > > > > > > Hi, > > > > > > > > > > I'm new to using Xalan and I tried to build a binary from the > source > > > > > code of > > > > > version 1.7.0 (using VC 6.0), but I got the following error > > messages: > > > > > > > > > > ..\..\..\..\src\xalanc\PlatformSupport\XalanMessageLoader.hpp(67): > > > > > fatal error C1083: Cannot open include file: 'LocalMsgIndex.hpp': > > > > > No such file or directory > > > > > > > > > > I put all the necessary Xerces dependencies to the project options > > and > > > > > started to build the AllInOne-Project (is set as active project > with > > > its > > > > > dependency). As I saw in the archive several others did have the > > same > > > > > problem. Somebody mentioned that the necessary header-file would > be > > > > > built at > > > > > compile-time but I still get the error - nothing is built at > > > > > compile-time.... > > > > > > > > > > Does anybody have any ideas? > > > > > > > > > > Thanks in advance, > > > > > Bettina > > > > > > > > > > -- > > > > > "Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim > > Surfen! > > > > > Jetzt aktivieren unter http://www.gmx.net/info > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > NEU : GMX Internet.FreeDSL > > > > Ab sofort DSL-Tarif ohne Grundgeb�hr: http://www.gmx.net/dsl > > > > > > > > > > > > > > > > > > > > > > -- > > > NEU : GMX Internet.FreeDSL > > > Ab sofort DSL-Tarif ohne Grundgeb�hr: http://www.gmx.net/dsl > > > > > > > > > > > > > > > > -- > > NEU : GMX Internet.FreeDSL > > Ab sofort DSL-Tarif ohne Grundgeb�hr: http://www.gmx.net/dsl > > > > > > > > > > -- > "Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen! > Jetzt aktivieren unter http://www.gmx.net/info > > > > -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgeb�hr: http://www.gmx.net/dsl
