Compiled SDL in VC2010, did I do it wrong?

…because when I send out my release builds people need MSVCR100.dll to run it. MSFT says I built my exe incorrectly but I used their 2010 defaults and their 2008 defaults don’t do this.

…because when I send out my release builds people need MSVCR100.dll to
run it. MSFT says I built my exe incorrectly but I used their 2010 defaults
and their 2008 defaults don’t do this.

You can remove the dependency on the MS* DLL files but changing the C++/Code
Generation setting to Multi-threaded Debug (/MTd) instead of Mult-Threaded
Debug DLL (/MDd). Make sure all SDL libraries you use are compiled with
this Code Generation setting, and your app also uses the same setting.

Despite what some people on this forum have said, that doesn’t violate the
SDL license since you are just changing how it links to the MS libraries,
you are not changing your code to link with SDL as a static LIB.

Ken RogowayFrom: sdl-bounces@lists.libsdl.org [mailto:sdl-bounces at lists.libsdl.org] On
Behalf Of avocados
Sent: Monday, June 21, 2010 11:22 PM
To: sdl at lists.libsdl.org
Subject: [SDL] Compiled SDL in VC2010, did I do it wrong?

The LGPL does not bar you from statically linking to SDL as long as
you provide the means to link to a different SDL lib. This includes
releasing your source code or compiled object files.On Tue, Jun 22, 2010 at 2:10 PM, Ken Rogoway wrote:

Despite what some people on this forum have said, that doesn?t violate the
SDL license since you are just changing how it links to the MS libraries,
you are not changing your code to link with SDL as a static LIB.


http://codebad.com/