> On Mar 4, 2004, at 2:49 PM, [EMAIL PROTECTED] wrote:
>
> > Even if you are using the Intel compiler for most of the code, it
> > should
> > not be a problem to use the Microsoft compiler for the message library,
> > which is all that is built by the Localization target. As far as I
> > know,
> > you can switch compilers within the IDE after you've installed the
> > Intel
> > compiler.
>
> It's not quite that simple. The compiler doesn't actually seem to be
> the problem (unless the compiled MsgCreator.exe is screwed up). When I
> run MsgCreator.exe at the command line, I get a similar problem:
>
> C:\build\Xalan-C_1_7_0-src\c\Build\Win32\VC6\Release>MsgCreator
> ..\..\..\..\..\src\xalanc\NLS\en_US\XalanMsg_en_US.xlf -TYPE icu
> -LOCALE en_US
>
> General error occured.
>
> I'd imagine that this is why the build is failing. Has anybody seen
> this problem before?
No, I've never seen that before, but it's coming from a catch (...) handler
within the application, so it sounds like something really bad is happening
inside of Xerces-C or inside the handler that builds the message file. You
might try building the debug configuration and running it in the debugger
to see what's happening.
> > I'm not sure how Xerces-C builds through the command line. Do they
> > export
> > makefiles? You could easily do the same thing within the Microsoft
> > IDE.
>
> There is a command line utility to build using the project file, which
> they set up correctly using a perl script. I'm not sure how much other
> voodoo was involved (you add a command line option for using the ICU
> transcoder, and everything just builds).
Are you referring to the packageBinaries.pl perl script? If so, it
launches the IDE from the command line in batch mode, and there's no reason
why you can't do that for Xalan-C as well.
Dave
