I want to clear up some misinformation on this topic. I had run into a lot
of problems following another post that said to use the Windows 7.1 SDK.
If you use the Windows 7.1 SDL with Visual Studio 2005, you will run into
some major link issues. You’ll get some “file corrupt” link errors. Google
and you will find there is a hotfix to get around this, but if you install
the hotfix you will have problems with older libraries, so I’d recommend you
don’t do that.
It turns out that you can use the 6.0A or 7.0 SDK files to get SDL to
compile under Windows. There is no need for the 7.1 SDK.
Sam, consider this “bug” fixed, as it works fine with the Windows 6.0A SDK.
For anyone looking to get SDL 1.3.0 to compile with VS2005, make sure you
add:
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Include to your
Project Directories Include
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib to your
Project Directories Lib
These are under Tools/Options/Projects and Solutions/VC++ Directories
KenFrom: slouken@gmail.com [mailto:slouken at gmail.com] On Behalf Of Sam Lantinga
Sent: Saturday, January 22, 2011 10:40 PM
To: Ken Rogoway
Subject: Re: [SDL] SDL and Visual Studio 2005
Thanks! I’ll look at it on Monday. 
On Sat, Jan 22, 2011 at 7:53 PM, Ken Rogoway <@Ken_Rogoway> wrote:
I’ve filed a bug for this.
From: sdl-bounces@lists.libsdl.org [mailto:sdl-bounces at lists.libsdl.org] On
Behalf Of Ken Rogoway
Sent: Saturday, January 22, 2011 4:38 PM
To: 'SDL Development List’
Subject: Re: [SDL] SDL and Visual Studio 2005
Sure, but I cannot get to the link issues when I remove the 7.1 include
because of the dependency on:
msctf.h
Ken
From: sdl-bounces@lists.libsdl.org [mailto:sdl-bounces at lists.libsdl.org] On
Behalf Of Sam Lantinga
Sent: Saturday, January 22, 2011 3:56 PM
To: SDL Development List
Subject: Re: [SDL] SDL and Visual Studio 2005
No, SDL shouldn’t require the 7.1 SDK. It should be optional, or at the
very least possible to disable.
Can you submit a bug for the error messages you get if you don’t have it
installed?
Thanks!
On Sat, Jan 22, 2011 at 1:09 PM, Ken Rogoway <@Ken_Rogoway> wrote:
Recent changes to SDL 1.3 require the Windows 7.1 SDK. Although this does
work, it requires an update hotfix for Visual Studio 2005 to get around the
"corrupt library" problem between the SDK and VS2005. Unfortunately this
now means that all of my other projects (non-SDL related) no longer link
because of conflicts between the SDK 7.1 libraries and the libraries that
are shipped with VS2005.
I found one (horrible) work around online, but it required renaming
individual LIB files in the VS2005 lib folder.
Do we really need to have SDL dependent on these new features in the Windows
7.1 SDK? I believe they were for IMM or IME stuff.
With a lot of other “features” we have macros to enable/disable them. If I
knew what exactly we gained by using the 7.1 SDK I could decide if it is
worthwhile changing 30+ non-SDL projects just to support this change in SDL
for my 1 SDL project.
Ken
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
–
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
–
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC