The library naming convention has already been changed since Xerces-C++ 2.0, and so-name has been used wherever applicable. See http://xml.apache.org/xerces-c/migrate_archive.html#LibraryChange200 for details.
Tinny ----- Original Message ----- From: "Murray Cumming" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 04, 2002 12:02 PM Subject: RE: Proposal Review: Using C++ Namespace > On Mon, 2002-11-04 at 17:17, Brad Settlemyer wrote: > > > -----Original Message----- > > > From: Murray Cumming [mailto:murrayc@;t-online.de] > > > Major "API versions" absolutely should be in the library name. How else > > > will an application benefit from bugfixes in the Xerces-C++ library that > > > is uses, without relinking that application against a new version of the > > > library. This is all quite normal. > > > > > > > I think I may have been unclear here. On UNIX systems, the library > > mechanism has explicit support for versioning uses naming suffixes. Xerces > > does not use those, instead it embeds the version number into the name. > > E.g., rather than libxerces.so.1.7.0 we get libxerces_1_7_0.so.0.0.0, or > > something like that. This means I have to explicitly link to a specific > > release number rather than to a major release or version if I use their > > library. > > Yes, that's obviously silly. I think it's been improved in 2.x. I can't > know for sure because _no_ library is installed at the moment. Just > taking the chance to say that again on the mailing list, in the hope of > a response. > > -- > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
