Should default MSVC static library build use shared DLL runtime library instead of static?

View: New views
2 Messages — Rating Filter:   Alert me  

Should default MSVC static library build use shared DLL runtime library instead of static?

by Timie Milie :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


I guess it might just come down to a matter of preference but while I
don't want a DLL dependency on Crypto++ (so I use it as a static
library) I don't wan't to use the runtime as a static library (as this
can be found on most computers). If I am not unusual in the latter
preferrence is it worth changing this default setting in the MVC
project on subsequent releases (not doing so creates multiple (re)
defined runtime function errors should anyone by wondering)?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---


Re: Should default MSVC static library build use shared DLL runtime library instead of static?

by Robert Roessler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Timie Milie wrote:
> I guess it might just come down to a matter of preference but while I
> don't want a DLL dependency on Crypto++ (so I use it as a static
> library) I don't wan't to use the runtime as a static library (as this
> can be found on most computers). If I am not unusual in the latter
> preferrence is it worth changing this default setting in the MVC
> project on subsequent releases (not doing so creates multiple (re)
> defined runtime function errors should anyone by wondering)?

You might want to reconsider this... VC6 was the last compiler that
would generate code using msvcrt.dll (for non-static builds).

There are actually 2 issues here - not only do the newer (starting with
VC7 in VS 2002) MS compilers not use the older runtime DLL, the newer
C/C++ runtime DLLs are no longer considered a part of Windows - so the
newer ones do not come along with Windows service packs.

And all of this is in addition to the weird problems that will
eventually crop up with (if I understood you correctly) trying to build
apps that use both the static and dynamic runtimes.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---