Building regular DLL based on static libs compiled with _AFXDLL

Question

I am trying to build a regular DLL that depends upon a set of static libs I get from elsewhere. The static libs are compiled with _AFXDLL and _AFXEXT and /MD. (The static libs are used by a different application that uses shared MFC libs.)
I can link the dll, but when it runs it fails to find CRuntimeType information for classes in those static libs. Specifically, some source in the static libs is calling:
AFX_MODULE_STATE *afxs = AfxGetModuleState();
and looking thru the afxs->m_classList which happens to be NULL. (There should be lots of classes there.)
Currently my regular DLL is linking agains the static MFC libs.
To be clear, I do not want to export any MFC classes from my dll, the MFC classes are only used internally by the static libs I'm linking my dll against. That's why I am using a regular (not mfx extension) dll.
Do I need to link my dll with shared mfc? I have a fair amount of exported functions. I would have to add
AFX_MANAGE_STATE(AfxGetStaticModuleState( ))
to every exported function right?

Answer 1

Ok, I've tried a few things and I know more of what's going on.
I linked my dll with the shared mfc (_AFXDLL) and added the AFX_MANAGE_STATE(AfxGetStaticModuleState( )) to some of the exported functions to try it out. It switches to the dll's AFX_MODULE_STATE alright, but the class list is empty. If I break in the CWinApp initializer (before any exported functions are called) for the dll, the class list is there. So where did it go?
Well I stepped thru in the debugger and here's what's happening:
_CRT_INIT creates the AFX_MODULE_STATE for the dll and AfxClassInit() gets called lots of times to add the runtime class info. Looks like this is being done by static constructors in the static libs I'm linking my dll against. So far so good.
Then after that, InternalDllMain comes along and calls AfxInitExtensionModule( state, ... )
Here's the problem, AfxInitExtensionModule, in addition to modifing it's state argument like you would expect it to, it also has this curious line:
pModuleState->m_classList.m_pHead = pModuleState->m_pClassInit;
where pModuleState is the current (dll's) state. So my class list is wiped out because the m_pClassInit slot is NULL. The AFX_MODULE_STATE constructer sets the m_pClassInit member to NULL. Looks like it's supposed to be some kind of backup so I have no clue what AfxInitExtensionModule is doing what it's doing.
Is this a bug or do I still not have something set up right???