Unix exports everything, which is something I think is a bad thing. But, it means you never fail to have something in a library, even if you weren't intended to have that access. In Windows it must be explicitly exported, else its considered an internal detail.
-------------------------- Dean Roddey The Charmed Quark Controller Charmed Quark Software [EMAIL PROTECTED] http://www.charmedquark.com "If it don't have a control port, don't buy it!" ----- Original Message ----- From: "Jason E. Stewart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 12:53 PM Subject: Re: Xerces C++ Exceptions not Exported > "Robert Buck" <[EMAIL PROTECTED]> writes: > > > Using Visual Studio I link my application against Xerces and ICU. If > > I use either of those specific classes in my code I get unresolved > > link errors. The other exception types are exported in the API's and > > I have no problem with those. In fact, when I check the xerces dlls > > with a depends tool, neither of these two classes are exported. The > > header file confirms this. > > This is a windows-specific issue then. It works perfectly under > Unix. > > I'll let Tinny or someone else with windows knowledge help. > jas. > > --------------------------------------------------------------------- > 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]
