Andy Heninger wrote:
> 
> Are you using the "packageBinaries.pl" script from Xerces to do the build?
> There's a fair amount of twiddling that happens to switch the xerces build
> from stand-alone mode to the use of ICU, and this script automates it.  It
> is also what the xerces group uses to do its full builds of XML4C.   In
> XML4C mode, the script will build both ICU and Xerces from scratch.  You
> shouldn't build ICU separately.

Nope - didn't know about packageBinaries.pl.  I thought runConfigure and
runConfigureICU were the documented ways to build.  Looks like I'll have to
wrestle with it a bit but I'm sure this is the way - thanks much!

-- 
  Jack Marr ([EMAIL PROTECTED]) Cypress, CA
  Unigraphics Solutions - NYSE:UGS - http://www.ugsolutions.com

> 
> ----- Original Message -----
> From: "Jack Marr" <[EMAIL PROTECTED]>
> To: "ICU Mailing List" <[EMAIL PROTECTED]>
> Sent: Tuesday, July 03, 2001 10:29 AM
> Subject: Problem building XML4C on Solaris and Irix
> 
> > I'm trying to build XML4C 3.5.0 from sources provided by
> > http://www.alphaworks.ibm.com/tech/xml4c, but am stymied at the point
> where it
> > wants to link Xerces with ICU because it is looking for libicudata.so,
> but such
> > a beast isn't produced by the icu 1.8.1 scripts.  Those scripts produce
> > libicudt18b.so and icudata.so (no "lib" prefix), and I suppose I could
> rename
> > that file to be what Xerces wants to see, but it seems to me this should
> not
> > require my manual intervention, so I'm wondering what step I'm missing.
> I
> > notice the binary downloads for AIX and HP-UX both contain a
> libicudata.*, so
> > whoever built XML4C for those platforms found the missing link.  Perhaps
> someone
> > can point me in the right direction.
> >
> >
> 
> _______________________________________________
> icu mailing list
> [EMAIL PROTECTED]
> http://oss.software.ibm.com/developerworks/opensource/mailman/listinfo/icu

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to