Oliver, I have been getting around these complexities by building the AllInOne project which puts everything in one library. Have found it much easier, and given it's in line with the plan for the next release it worked well.
Cheers, Berin > > From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]> > Subject: Re: Problem linking a release build > Date: 29/01/2003 11:58:55 > To: [email protected] > > > > > > Hi Oliver, > > You probably just need to add another library for the release build. Make > sure you're linking against XalanDOM_1.lib for the release build. You > don't need this for the debug build because the compiler is doing different > code generation in Debug (it's putting an out-of-line copy in each > compilation unit.) > > The next release will consolidate all of the Xalan DLLs into one DLL, which > will make this simpler. > > Dave > > > > > > [EMAIL PROTECTED] > > ensys.com To: > [email protected] > > cc: (bcc: David N > Bertoni/Cambridge/IBM) > 01/28/2003 04:45 Subject: Problem linking a > release build > PM > > > > > > > Hi folks, > > I'm trying to create a release build of Xalan with VC++ 6.0. I have copied > the link settings, changing the relevant xerces and xalan libs from the ' > _1D' version to '_1' (I'm using xerces 2.1 and xalan 1.4). However, I get > this linking problem: > > ValidationManager.lib(CSchematronValidator.obj) : error LNK2001: unresolved > external symbol "__declspec(dllimport) public: __thiscall XalanDOMString:: > ~XalanDOMString(void)" (__imp_??1XalanDOMString@@[EMAIL PROTECTED]) > > Are there extra libraries necessary for the release build? > > Any help would be most appreciated. > > -- > Oli > > > > This message was sent through MyMail http://www.mymail.com.au
