On 10 Jun 2003, Jason E. Stewart wrote: > Hey All, > > I've finally solved the namespace compilation issues that crept up in > Xerces-C-2.2 - just in time to make a release for Xerces-C-2.3! > > I've just uploaded the code to: > > http://xml.apache.org/dist/xerces-p/experimental/ > > It includes some important changes to the build environment. Notably, > it now uses the config.status file from Xerces-C to configure the > build process: the compiler, the compiler flags, and the linker > flags. This should make building XML::Xerces on OS's other than linux > *much* simpler. If you built Xerces-C from source and have defined the > XERCESCROOT variable, Makefile.PL will locate config.status for > you. If you are using a Xerces-C binary, then you need to set the > XERCES_CONFIG variable to point to the file. > > It would be a big help if people with access to different OS's and > compilers could test this out - I will be most grateful, and happy to > make mods for your configuration.
Jason, I almost have XML::Xerces-2.3.0-0 building against xml4c (Xerces 2.2.0). The problem I'm tripping over is that for some reason I do not end up with this sort of declaration in Xerces.pm: use vars qw(@ISA %OWNER %ITERATORS %BLESSEDMEMBERS); leading to 1,000s of runtime errors due to undeclared variables. I'm using the same version of swig (1.3.17u) that you appear to be. Are you truly distributing the necessary set of configuration or pre/post process files? Or is there some other magic incantation required to do a build "from scratch" (i.e. after deleting Xerces.C and Xerces.pm)? The only change necessary so far was to slightly change the call convention to XMLPlatformUtils::fgTransService->makeNewTranscoderFor(...) by eliminating the (I'm guessing) newly-added fourth parm. And, of course, I had to change the expected level of Xerces in Makefile.PL. Steve -- ---------------------------------------------------------------- Steven N. Hirsch tie-line: 446-6557 ext: 802-769-6557 Staff Engineer Methodology Integration Team ASIC Product Development IBM Microelectronics ---------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
