Compiling SDL2 with VS2012 on Windows 8

Hey all,

I downloaded the latest stable source and tried to use the SDL_VS2012
solution included in the VisualC folder to build the source.

I was met with an angry:
error C1083: Cannot open include file: ‘dxsdkver.h’: No such file or
directory

This indicates that the DirectX SDK headers can’t be found, so I checked
the project’s include directories and noticed this:
$(DXSDK_DIR)\Include

Unfortunately, I don’t have this macro in my list, so I did some research.
Turns out that the DirectX SDK was rolled up into the Windows SDK with the
release of Windows 8 and Visual Studio 2012. The macro that Microsoft
suggests now is:
$(WindowsSDK_IncludePath)

Using that macro instead still didn’t work, so I checked in the Windows SDK
includes directory manually and couldn’t even find the ‘dxsdkver.h’ header.
Is it included in the Windows SDK with Windows 8?

Has anyone else run into this?

Thanks.

Replying to myself with more information.

I downloaded the June 2010 DirectX SDK which did include dxsdkver.h and the
build succeeded. Anyone know if Microsoft moved the functionality of that
header somewhere else or renamed it in the Windows 8 SDK?On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles <@Justin_Skiles>wrote:

Hey all,

I downloaded the latest stable source and tried to use the SDL_VS2012
solution included in the VisualC folder to build the source.

I was met with an angry:
error C1083: Cannot open include file: ‘dxsdkver.h’: No such file or
directory

This indicates that the DirectX SDK headers can’t be found, so I checked
the project’s include directories and noticed this:
$(DXSDK_DIR)\Include

Unfortunately, I don’t have this macro in my list, so I did some research.
Turns out that the DirectX SDK was rolled up into the Windows SDK with the
release of Windows 8 and Visual Studio 2012. The macro that Microsoft
suggests now is:
$(WindowsSDK_IncludePath)

Using that macro instead still didn’t work, so I checked in the Windows
SDK includes directory manually and couldn’t even find the 'dxsdkver.h’
header. Is it included in the Windows SDK with Windows 8?

Has anyone else run into this?

Thanks.

iirc, You need to add the DirectX SDK add the include and lib folders to
the compiler’s include and library paths respectively. I’m not on Windows
right now, so I can’t confirm their exact paths, but it should be something
like C:\Program Files\DirectX SDK June 2010{include, lib} , but you’d have
to check that out yourself.

Hope that helps,
-AlexOn Tue, Oct 22, 2013 at 5:02 PM, Justin Skiles <justin.d.skiles at gmail.com>wrote:

Replying to myself with more information.

I downloaded the June 2010 DirectX SDK which did include dxsdkver.h and
the build succeeded. Anyone know if Microsoft moved the functionality of
that header somewhere else or renamed it in the Windows 8 SDK?

On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles <justin.d.skiles at gmail.com>wrote:

Hey all,

I downloaded the latest stable source and tried to use the SDL_VS2012
solution included in the VisualC folder to build the source.

I was met with an angry:
error C1083: Cannot open include file: ‘dxsdkver.h’: No such file or
directory

This indicates that the DirectX SDK headers can’t be found, so I checked
the project’s include directories and noticed this:
$(DXSDK_DIR)\Include

Unfortunately, I don’t have this macro in my list, so I did some
research. Turns out that the DirectX SDK was rolled up into the Windows SDK
with the release of Windows 8 and Visual Studio 2012. The macro that
Microsoft suggests now is:
$(WindowsSDK_IncludePath)

Using that macro instead still didn’t work, so I checked in the Windows
SDK includes directory manually and couldn’t even find the 'dxsdkver.h’
header. Is it included in the Windows SDK with Windows 8?

Has anyone else run into this?

Thanks.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Alex, thanks for the response. The solutions included in the source already
have the includes and libs directories in the project settings. However,
the locations are no longer valid in the Windows 8 and Windows 8.1 SDKs,
since Microsoft merged DirectX into the Windows SDK. Headers are gone,
renamed, and moved, so it’s a bit confusing. For the foreseeable future,
I’ll just continue building against the June 2010 DirectX SDK.On Tue, Oct 22, 2013 at 7:42 PM, Alex Barry <alex.barry at gmail.com> wrote:

iirc, You need to add the DirectX SDK add the include and lib folders to
the compiler’s include and library paths respectively. I’m not on Windows
right now, so I can’t confirm their exact paths, but it should be something
like C:\Program Files\DirectX SDK June 2010{include, lib} , but you’d have
to check that out yourself.

Hope that helps,
-Alex

On Tue, Oct 22, 2013 at 5:02 PM, Justin Skiles <@Justin_Skiles>wrote:

Replying to myself with more information.

I downloaded the June 2010 DirectX SDK which did include dxsdkver.h and
the build succeeded. Anyone know if Microsoft moved the functionality of
that header somewhere else or renamed it in the Windows 8 SDK?

On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles <@Justin_Skiles wrote:

Hey all,

I downloaded the latest stable source and tried to use the SDL_VS2012
solution included in the VisualC folder to build the source.

I was met with an angry:
error C1083: Cannot open include file: ‘dxsdkver.h’: No such file or
directory

This indicates that the DirectX SDK headers can’t be found, so I checked
the project’s include directories and noticed this:
$(DXSDK_DIR)\Include

Unfortunately, I don’t have this macro in my list, so I did some
research. Turns out that the DirectX SDK was rolled up into the Windows SDK
with the release of Windows 8 and Visual Studio 2012. The macro that
Microsoft suggests now is:
$(WindowsSDK_IncludePath)

Using that macro instead still didn’t work, so I checked in the Windows
SDK includes directory manually and couldn’t even find the 'dxsdkver.h’
header. Is it included in the Windows SDK with Windows 8?

Has anyone else run into this?

Thanks.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Hi Justin,

could you open a bug on bugzilla (https://bugzilla.libsdl.org) to track
this.

There seem to be a whole bunch of changes needed:
http://msdn.microsoft.com/en-us/library/windows/desktop/ee663275(v=vs.85).aspx

Thanks,
AndreasOn 10/22/2013 5:45 PM, Justin Skiles wrote:

Alex, thanks for the response. The solutions included in the source
already have the includes and libs directories in the project
settings. However, the locations are no longer valid in the Windows 8
and Windows 8.1 SDKs, since Microsoft merged DirectX into the Windows
SDK. Headers are gone, renamed, and moved, so it’s a bit confusing.
For the foreseeable future, I’ll just continue building against the
June 2010 DirectX SDK.

On Tue, Oct 22, 2013 at 7:42 PM, Alex Barry <alex.barry at gmail.com <mailto:alex.barry at gmail.com>> wrote:

iirc, You need to add the DirectX SDK add the include and lib
folders to the compiler's include and library paths respectively.
 I'm not on Windows right now, so I can't confirm their exact
paths, but it should be something like C:\Program Files\DirectX
SDK June 2010\{include, lib} , but you'd have to check that out
yourself.

Hope that helps,
-Alex


On Tue, Oct 22, 2013 at 5:02 PM, Justin Skiles <justin.d.skiles at gmail.com <mailto:justin.d.skiles at gmail.com>> wrote:

    Replying to myself with more information.


    I downloaded the June 2010 DirectX SDK which did include
    dxsdkver.h and the build succeeded. Anyone know if Microsoft
    moved the functionality of that header somewhere else or
    renamed it in the Windows 8 SDK?


    On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles <justin.d.skiles at gmail.com <mailto:justin.d.skiles at gmail.com>> wrote:

        Hey all,

        I downloaded the latest stable source and tried to use the
        SDL_VS2012 solution included in the VisualC folder to
        build the source.

        I was met with an angry:
        error C1083: Cannot open include file: 'dxsdkver.h': No
        such file or directory

        This indicates that the DirectX SDK headers can't be
        found, so I checked the project's include directories and
        noticed this:
        $(DXSDK_DIR)\Include

        Unfortunately, I don't have this macro in my list, so I
        did some research. Turns out that the DirectX SDK was
        rolled up into the Windows SDK with the release of Windows
        8 and Visual Studio 2012. The macro that Microsoft
        suggests now is:
        $(WindowsSDK_IncludePath)

        Using that macro instead still didn't work, so I checked
        in the Windows SDK includes directory manually and
        couldn't even find the 'dxsdkver.h' header. Is it included
        in the Windows SDK with Windows 8?

        Has anyone else run into this?

        Thanks.



    _______________________________________________
    SDL mailing list
    SDL at lists.libsdl.org <mailto:SDL at lists.libsdl.org>
    http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org



_______________________________________________
SDL mailing list
SDL at lists.libsdl.org <mailto:SDL at lists.libsdl.org>
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

I have Windows 8 64bit Pro and also couldn’t compile SDL2 with Visual
Studio 2012 Express
due to “error C1083: Cannot open include file: ‘dxsdkver.h’: No such file
or directory”.

I managed to compile it and works fine too when I took completely out
’dxsdkver.h’ from the header.
It compiled with a warning: That my Direct X is too old and will not run
XAudio2.
Other than that everything works fine and I did not install any DirectX
SDK.

Also tried to compile SDL_ttf with the same system and it gives hundreds
of errors.
This is broken.

Thanks,
Giorgos> ----- Original Message -----

Subject: Re: [SDL] Compiling SDL2 with VS2012 on Windows 8
From: Andreas Schiffler
To: SDL Development List
Date: 23/10/2013 04:43

Hi Justin,

could you open a bug on bugzilla (https://bugzilla.libsdl.org) to track
this.

There seem to be a whole bunch of changes needed:
http://msdn.microsoft.com/en-us/library/windows/desktop/ee663275(v=vs.85).aspx

Thanks,
Andreas

On 10/22/2013 5:45 PM, Justin Skiles wrote:

Alex, thanks for the response. The solutions included in the source
already have the includes and libs directories in the project
settings. However, the locations are no longer valid in the Windows 8
and Windows 8.1 SDKs, since Microsoft merged DirectX into the Windows
SDK. Headers are gone, renamed, and moved, so it's a bit confusing.
For the foreseeable future, I'll just continue building against the
June 2010 DirectX SDK.

On Tue, Oct 22, 2013 at 7:42 PM, Alex Barry <alex.barry@gmail.com> wrote:

  iirc, You need to add the DirectX SDK add the include and lib
  folders to the compiler's include and library paths respectively.
  I'm not on Windows right now, so I can't confirm their exact paths,
  but it should be something like C:\Program Files\DirectX SDK June
  2010\{include, lib} , but you'd have to check that out yourself.
  Hope that helps,
  -Alex

  On Tue, Oct 22, 2013 at 5:02 PM, Justin Skiles <justin.d.skiles@gmail.com> wrote:

    Replying to myself with more information.

    I downloaded the June 2010 DirectX SDK which did include
    dxsdkver.h and the build succeeded. Anyone know if Microsoft moved
    the functionality of that header somewhere else or renamed it in
    the Windows 8 SDK?

    On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles <justin.d.skiles@gmail.com> wrote:

      Hey all,
      I downloaded the latest stable source and tried to use the
      SDL_VS2012 solution included in the VisualC folder to build the
      source.

      I was met with an angry:
      error C1083: Cannot open include file: 'dxsdkver.h': No such
      file or directory

      This indicates that the DirectX SDK headers can't be found, so I
      checked the project's include directories and noticed this:
      $(DXSDK_DIR)\Include
      Unfortunately, I don't have this macro in my list, so I did some
      research. Turns out that the DirectX SDK was rolled up into the
      Windows SDK with the release of Windows 8 and Visual Studio
      2012. The macro that Microsoft suggests now is:
      $(WindowsSDK_IncludePath)

      Using that macro instead still didn't work, so I checked in the
      Windows SDK includes directory manually and couldn't even find
      the 'dxsdkver.h' header. Is it included in the Windows SDK with
      Windows 8?

      Has anyone else run into this?

      Thanks.

    _______________________________________________
    SDL mailing list
    SDL@lists.libsdl.org
    http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

  _______________________________________________
  SDL mailing list
  SDL@lists.libsdl.org
  http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

SDL mailing list
SDL@lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing list
SDL@lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

dxsdkver.h is no longer included in Windows8 SDK. Also, the version of
XAudio2 shipping with Win8 SDK does not work on PCs with earlier versions
of Windows (unless you go through some contortions mentioned in the msdn
doc on the subject). So it is probably best to comment out dxsdkver,h and
compile or link with an older SDK.On Wed, Oct 23, 2013 at 10:55 AM, Giorgos Sarris wrote:

I have Windows 8 64bit Pro and also couldn’t compile SDL2 with Visual
Studio 2012 Express
due to “error C1083: Cannot open include file: ‘dxsdkver.h’: No such file
or directory”.

I managed to compile it and works fine too when I took completely out
’dxsdkver.h’ from the header.
It compiled with a warning: That my Direct X is too old and will not run
XAudio2.
Other than that everything works fine and I did not install any DirectX
SDK.

Also tried to compile SDL_ttf with the same system and it gives hundreds
of errors.
This is broken.

Thanks,
Giorgos

-------- Original Message --------
Subject: Re: [SDL] Compiling SDL2 with VS2012 on Windows 8
From: Andreas Schiffler
To: SDL Development List
Date: 23/10/2013 04:43

Hi Justin,

could you open a bug on bugzilla (https://bugzilla.libsdl.org) to track
this.

There seem to be a whole bunch of changes needed:

http://msdn.microsoft.com/en-us/library/windows/desktop/ee663275(v=vs.85).aspx

Thanks,
Andreas

On 10/22/2013 5:45 PM, Justin Skiles wrote:

Alex, thanks for the response. The solutions included in the source
already have the includes and libs directories in the project settings.
However, the locations are no longer valid in the Windows 8 and Windows 8.1
SDKs, since Microsoft merged DirectX into the Windows SDK. Headers are
gone, renamed, and moved, so it’s a bit confusing. For the foreseeable
future, I’ll just continue building against the June 2010 DirectX SDK.

On Tue, Oct 22, 2013 at 7:42 PM, Alex Barry <alex.barry at gmail.com> wrote:

iirc, You need to add the DirectX SDK add the include and lib folders to
the compiler’s include and library paths respectively. I’m not on Windows
right now, so I can’t confirm their exact paths, but it should be something
like C:\Program Files\DirectX SDK June 2010{include, lib} , but you’d have
to check that out yourself.

Hope that helps,
-Alex

On Tue, Oct 22, 2013 at 5:02 PM, Justin Skiles < justin.d.skiles at gmail.com> wrote:

Replying to myself with more information.

I downloaded the June 2010 DirectX SDK which did include dxsdkver.h
and the build succeeded. Anyone know if Microsoft moved the functionality
of that header somewhere else or renamed it in the Windows 8 SDK?

On Tue, Oct 22, 2013 at 4:34 PM, Justin Skiles < justin.d.skiles at gmail.com> wrote:

Hey all,

I downloaded the latest stable source and tried to use the SDL_VS2012
solution included in the VisualC folder to build the source.

I was met with an angry:
error C1083: Cannot open include file: ‘dxsdkver.h’: No such file or
directory

This indicates that the DirectX SDK headers can’t be found, so I
checked the project’s include directories and noticed this:
$(DXSDK_DIR)\Include

Unfortunately, I don’t have this macro in my list, so I did some
research. Turns out that the DirectX SDK was rolled up into the Windows SDK
with the release of Windows 8 and Visual Studio 2012. The macro that
Microsoft suggests now is:
$(WindowsSDK_IncludePath)

Using that macro instead still didn’t work, so I checked in the
Windows SDK includes directory manually and couldn’t even find the
’dxsdkver.h’ header. Is it included in the Windows SDK with Windows 8?

Has anyone else run into this?

Thanks.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing listSDL at lists.libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing listSDL at lists.libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


Pallav Nawani
IronCode Gaming Private Limited
Website: http://www.ironcode.com
Twitter: http://twitter.com/Ironcode_Gaming
Facebook: http://www.facebook.com/Ironcode.Gaming
Mobile: 9997478768

Here’s some more info from Chuck Walbourn after I asked this question on an MSDN board.

http://social.msdn.microsoft.com/Forums/windowsapps/en-US/ca03a834-1108-4767-b19c-773cfd8a47e5/is-dxsdkverh-header-file-missing-from-the-windows-sdk-as-of-8-and-81?forum=windowssdk#ca03a834-1108-4767-b19c-773cfd8a47e5> You should remove the reference to dxsdkver.h. All it contained were the following #defines:

_DXSDK_PRODUCT_MAJOR
_DXSDK_PRODUCT_MINOR
_DXSDK_BUILD_MAJOR
_DXSDK_BUILD_MINOR

For more information on moving from the legacy DirectX SDK to the Windows 8.x SDK, see
http://blogs.msdn.com/b/chuckw/archive/2012/08/22/directx-sdk-s-of-a-certain-age.aspx
http://blogs.msdn.com/b/chuckw/archive/2013/07/01/where-is-the-directx-sdk-2013-edition.aspx
http://blogs.msdn.com/b/chuckw/archive/2013/08/21/living-without-d3dx.aspx

I’m getting the same problem on windows 7, shouldn’t the preprocessor commands somehow safeguard the build against such issues?------------------------
The best of us, find happiness in misery.