Can't compile SDL 1.3 using Visual Studio 2005

Hi friends!

I would like to use SDL 1.3 on Windows. I try to compile it (last snapshoot,
SDL-1.3.0-4537) and I get a lot errors like this:
fatal error C1083: Cannot open include file: ‘d3d9.h’: No such file or
directory
So, I guess I need DirectX9 SDK, right now I’ll look for it.

Questions:
Is there any TXT or document with HOWTO compile it and requirements or any
other instrucciones about compiling 1.3 on VS2005?
I only want to use OpenGL. Must I still download DX9SDK? (note: I will use a
joystick)
On project settings, I don’t see anything regarding directx pahts, should I
include them? (In the case I have to use it)

That’s all, thanks lot for your time.

Have you checked the FAQ?

http://www.libsdl.org/cgi/docwiki.cgi/FAQ_Frequently_Asked_Questions#head-640a7d4647ada5770da1612da60616e0f65fa127

It speaks about 2003 version, but there are not that many changes between
both versions.–
Paulo

On Tue, Jun 9, 2009 at 3:08 PM, Ricardo wrote:

Hi friends!

I would like to use SDL 1.3 on Windows. I try to compile it (last
snapshoot,
SDL-1.3.0-4537) and I get a lot errors like this:
fatal error C1083: Cannot open include file: ‘d3d9.h’: No such file or
directory
So, I guess I need DirectX9 SDK, right now I’ll look for it.

Questions:
Is there any TXT or document with HOWTO compile it and requirements or any
other instrucciones about compiling 1.3 on VS2005?
I only want to use OpenGL. Must I still download DX9SDK? (note: I will use
a
joystick)
On project settings, I don’t see anything regarding directx pahts, should I
include them? (In the case I have to use it)

That’s all, thanks lot for your time.


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

Perhaps this is the closer thread about compiling sdl
http://www.libsdl.org/cgi/docwiki.cgi/FAQ_Compiling_on_Microsoft_Visual_C%2B%2B_2005_Express
but it seems it is about SDL 1.2 and links to directx are broken.

Any other guida? Have anybody compiled SDL 1.3 with VS2005 sucessfully?

Thanks a lot for your time.

“Paulo Pinto” escribi? en el mensaje news:969dc8fe0906090807y7e759b03p1799b210989ef277 at mail.gmail.com
Have you checked the FAQ?

http://www.libsdl.org/cgi/docwiki.cgi/FAQ_Frequently_Asked_Questions#head-640a7d4647ada5770da1612da60616e0f65fa127

It speaks about 2003 version, but there are not that many changes between both versions.–
Paulo

On Tue, Jun 9, 2009 at 3:08 PM, Ricardo <@Ricardo> wrote:

Hi friends!

I would like to use SDL 1.3 on Windows. I try to compile it (last snapshoot,
SDL-1.3.0-4537) and I get a lot errors like this:
fatal error C1083: Cannot open include file: 'd3d9.h': No such file or
directory
So, I guess I need DirectX9 SDK, right now I'll look for it.

Questions:
Is there any TXT or document with HOWTO compile it and requirements or any
other instrucciones about compiling 1.3 on VS2005?
I only want to use OpenGL. Must I still download DX9SDK? (note: I will use a
joystick)
On project settings, I don't see anything regarding directx pahts, should I
include them? (In the case I have to use it)

That's all, thanks  lot for your time.



_______________________________________________
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

Any other guida? Have anybody compiled SDL 1.3 with VS2005 sucessfully?

I just tried it, here’s my list of steps:

  • Install VS2005 (The free-download Visual C++ Express 2005 works, too).

  • Install the latest DirectX SDK from Microsoft:

http://www.microsoft.com/downloads/details.aspx?FamilyID=24a541d6-0486-4453-8641-1eee9e21b282&displaylang=en

  • You may have to add it to VS2005 if the DirectX installer didn’t do
    it. In Visual Studio, go to the “Tools” menu, “Options”, “Projects and
    Solutions”, “VC++ Directories”, “Show Directories for:”, “Include files”
    … add “C:\Program Files\Microsoft DirectX SDK (March 2009)\Include”
    (or whatever) to the start of the list if something like that isn’t
    already there. Do the same with “Show directories for: Library Files”,
    adding “Lib\x86” instead of “Include”.

  • Check out SDL 1.3 from Subversion, open SDL/VisualC/SDL.sln in VS2005.

  • You’ll need to tweak two files in the SDL/include directory, that
    don’t get generated by Visual Studio. Move “SDL_config_win32.h” to
    "SDL_config.h" and make a file called “SDL_revision.h” that has this line:

    #define SDL_REVISION 0

  • Then, tell Visual Studio to build the solution. It should work.

Rather, it’ll work when the atomic operations patch is fixed, soon.

There is also a “test” solution in there, to build the example
applications. You can use this to sanity check things.

Some of those steps are a little opaque, but it’s not too hard.

–ryan.

I am out of the loop on 1.3v, but are we going to need DX SDK to compile
and run 1.3 now?

Ryan C. Gordon wrote:>

Any other guida? Have anybody compiled SDL 1.3 with VS2005 sucessfully?

I just tried it, here’s my list of steps:

  • Install VS2005 (The free-download Visual C++ Express 2005 works, too).

  • Install the latest DirectX SDK from Microsoft:

http://www.microsoft.com/downloads/details.aspx?FamilyID=24a541d6-0486-4453-8641-1eee9e21b282&displaylang=en

  • You may have to add it to VS2005 if the DirectX installer didn’t do
    it. In Visual Studio, go to the “Tools” menu, “Options”, “Projects and
    Solutions”, “VC++ Directories”, “Show Directories for:”, “Include
    files” … add “C:\Program Files\Microsoft DirectX SDK (March
    2009)\Include” (or whatever) to the start of the list if something
    like that isn’t already there. Do the same with “Show directories for:
    Library Files”, adding “Lib\x86” instead of “Include”.

  • Check out SDL 1.3 from Subversion, open SDL/VisualC/SDL.sln in VS2005.

  • You’ll need to tweak two files in the SDL/include directory, that
    don’t get generated by Visual Studio. Move “SDL_config_win32.h” to
    "SDL_config.h" and make a file called “SDL_revision.h” that has this
    line:

    #define SDL_REVISION 0

  • Then, tell Visual Studio to build the solution. It should work.

Rather, it’ll work when the atomic operations patch is fixed, soon.

There is also a “test” solution in there, to build the example
applications. You can use this to sanity check things.

Some of those steps are a little opaque, but it’s not too hard.

–ryan.


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

I am out of the loop on 1.3v, but are we going to need DX SDK to compile
and run 1.3 now?

Was there ever a time when you didn’t need the DirectX SDK to build SDL?

–ryan.

I am out of the loop on 1.3v, but are we going to need DX SDK to compile
and run 1.3 now?

Was there ever a time when you didn’t need the DirectX SDK to build SDL?

I’m far from a Windows expert, and I didn’t delve into the Win32 parts
of SDL very much, but now that the default backend on Windows is GDI
rather than DirectDraw, shouldn’t it be possible to build SDL without
DirectX? Or does it also use DirectInput, or some other part?On Wed, Jun 17, 2009 at 8:41 AM, Ryan C. Gordon wrote:


http://pphaneuf.livejournal.com/

As far as I know, you need to customize the build process for it to work, if
at all.

It is way much easier just to have the proper SDKs in place.-
Paulo

On Wed, Jun 17, 2009 at 6:26 PM, Pierre Phaneuf wrote:

On Wed, Jun 17, 2009 at 8:41 AM, Ryan C. Gordon wrote:

I am out of the loop on 1.3v, but are we going to need DX SDK to compile
and run 1.3 now?

Was there ever a time when you didn’t need the DirectX SDK to build SDL?

I’m far from a Windows expert, and I didn’t delve into the Win32 parts
of SDL very much, but now that the default backend on Windows is GDI
rather than DirectDraw, shouldn’t it be possible to build SDL without
DirectX? Or does it also use DirectInput, or some other part?


http://pphaneuf.livejournal.com/


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

As far as I know, you need to customize the build process for it to work, if
at all.

It is way much easier just to have the proper SDKs in place.

Ah, right no autoconf there, gotcha…On Wed, Jun 17, 2009 at 4:55 PM, Paulo Pinto wrote:


http://pphaneuf.livejournal.com/