Re: C-Run-time library static vs DLL vs both!

From:

"Giovanni Dicanio" <giovanni.dicanio@invalid.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 12 Jun 2008 12:19:46 +0200

Message-ID:

<#uXb7YHzIHA.2360@TK2MSFTNGP05.phx.gbl>

Hi Dave,

"David Webber" <dave@musical-dot-demon-dot-co.uk> ha scritto nel messaggio
news:OEtA$m$yIHA.1236@TK2MSFTNGP02.phx.gbl...

One cpp file:

============
#define WIN32_LEAN_AND_MEAN
#include <windows.h>

BOOL APIENTRY DllMain( HANDLE hModule,
                      DWORD ul_reason_for_call,
                      LPVOID lpReserved
     ) { return TRUE; }
============

Questions:
1. Does the above code actually need the C-Runtime library?

It seems that it is not calling any C-runtime function (printf, atof....)
.... however, I don't know if the linker needs to add some prologue-epilogue
code to that, behind the scenes...

2. If so, can I link some modules to it statically and others to the DLL?

I'm not sure if I understood the question well...
Does this question mean:
"Can I link some modules to CRT statically, and other modules to CRT DLL
(dynamically) ?"

I think the question is yes, if you pay attention to the fact that *any*
heap allocation that you do in a module which is statically-linked to CRT,
is freed by the *same* module (because I think that static-linked CRT heap
is different from dynamically-linked CRT heap).

Giovanni