Export classes in a DLL drived from classes exported by Xerces causes linker 
errors
-----------------------------------------------------------------------------------

                 Key: XERCESC-1855
                 URL: https://issues.apache.org/jira/browse/XERCESC-1855
             Project: Xerces-C++
          Issue Type: Bug
          Components: DOM
    Affects Versions: 3.0.1
         Environment: Windows XP Visual Studio 2005
            Reporter: Andrea Richards
            Priority: Blocker


We currently have a DLL which exports a couple of classes derived from Xerces. 
These are ContentSpecHandler and DTDElementDecl. When I try to export these 
classes from our DLL I get numerous linker errors despite including the both 
the lib files (which contain the correct signatures) and setting up the 
solutions dependancies.  One example is shown below. I believe this to be a bug 
as it must be possible to derive a class from Xerces in a another DLL and then 
export it to be used by an EXE file, but this appears not to be the case. Do 
you have an answer or a working solution that will allow me to continue 
integration ? Thanks

Andrea



class LAD_EXPORT CXMLContentSpecNode : public ContentSpecNode
{

   public:
      CXMLContentSpecNode(MemoryManager* const manager = 
XMLPlatformUtils::fgMemoryManager)
         : ContentSpecNode(manager), m_iElementId(-1) {};

...

};

Linker error :
XMLInterface.obj : error LNK2001: unresolved external symbol "public: static 
class xercesc_3_0::MemoryManager * 
xercesc_3_0::XMLPlatformUtils::fgMemoryManager" 
(?fgmemorymana...@xmlplatformutils@xercesc_3_0@@2pavmemorymana...@2@A)

Map file entry:
 0004:00030c7c       
?fgmemorymana...@xmlplatformutils@xercesc_3_0@@2pavmemorymana...@2@A 10552c7c   
  PlatformUtils.obj







-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to