The bad news is that I can't seem to retrofit the new localization addition into the OS X IDE easily. This is because the IDE doesn't have direct support for Makefile.in, which then generates the Makefile, which then generates the required *.hpp files. There's also the complication of building the MsgCreator first. If one spends enough time on it, it can probably be done but at this point, I just can't justify spending more efforts. I'm not sure how other IDEs are successful in dealing with these extra steps...
Any way, I guess Mac OS X developers can deal with the .so instead.
Cheers, Han Ming
On Dec 15, 2003, at 12:10 PM, Han Ming Ong wrote:
On Dec 15, 2003, at 11:53 AM, Dmitry Hayes wrote:
Hi Han Ming!
LocalMsgIndex.hpp is a part of the localization addition that still needs
some polishing .
But you should be able to build Xalan.
The file is missing , because it's supposed to be created in build time.
Please look at xml-xalan/c/src/xalanc/Utils/Makefile.in, "INMEM" section :
for creation the file we use a MsgCreator application.
For running the application (or for finding Xerces .so ) we use , for
example, LD_LIBRARY_PATH for the Linux platform.
There is no such environmental variable defined in the Mac section - it
should be added .
Dimitry,
You know what, I just ran into this problem and was about to file a bug :-)
It will be DYLD_LIBRARY_PATH for the Mac OS X platform.
As to June Ng's question about how I am building it...
- Xerces allows people to build it as either a shared library or a framework (another form of shared library in Mac OS X, essentially with resources).
- I'm trying to replicate the same building process as I think people will use Xerces before Xalan (that's just the way it is).
- A little while, when playing with Xalan1.6, I was successful in building it as a shared library and never really give any more thoughts to that. I supplied the Project Builder project files to enable to build as a Framework but that's not too successful for other people (for me, it was OK).
- Apple has since release an upgrade IDE known as Xcode. Xerces has moved on to it. I would like to upgrade Xalan to using Xcode as well. And that's how I'm building. If there is an extra step to run MsgCreator as a binary, I can add that as shell-script step to Xcode. But making that step dynamic enough so that it knows where to find the Xerces framework might or might not be tricky. I got to try that.
- I just tried build Xalan as a shared library using the runConfigure way and ran into the problem that Dimitry mentioned. After setting DYLD_LIBRARY_PATH as an extra step in the Terminal, I was able to build it as a shared library.
You must have your reasons to introduce such a dynamic code-gen step during compilation but it does complicate things a little...
Han Ming
Thanks, Dmitry
----- Forwarded by Dmitry Hayes/Toronto/IBM on 12/15/2003 02:14 PM -----
|---------+----------------------------> | | Han Ming Ong | | | <[EMAIL PROTECTED]| | | m> | | | | | | 12/15/2003 01:46 | | | PM | | | Please respond to| | | xalan-dev | |---------+---------------------------->--------------------------------------------------------------------- ---------------------------------------------------------|| |
| To: [EMAIL PROTECTED] |
| cc: |
| Subject: Re: [VOTE} Xalan 1.7 release plan |--------------------------------------------------------------------- ---------------------------------------------------------|
On Dec 11, 2003, at 9:14 AM, [EMAIL PROTECTED] wrote:
Hi folks,
It's time to start thinking about doing a Xalan-C release that is compatible with the latest Xerces-C 2.4 release.
... ... [snipped] ...If anyone else would like to volunteer their services, please let us know. We need someone to try a MacOS build with the latest code in cvs and flush out any build/runtime problems as we don't have an environment ourselves to do this work.
While I'm doing some stuff on Xerces, I can try to help build Xalan as
well. As of today, I tried to upgrade the current Project Builder to
the new Mac OS X IDE Xcode. There is a problem: while compiling, Xcode
complains that it couldn't locate LocalMsgIndex.hpp which is referenced
in XalanMessageLoader.hpp.
I couldn't find LocalMsgIndex.hpp on the CVS file system as well. A quick search on the current bug list reveals nothing about it.
Anyone?
thanks, Han Ming
