So SDL and the recently updated SDL satellite libraries have been updated
to SDL 2.0 in Mercurial:
http://hg.libsdl.org
I haven’t updated the website yet, but those of you who want to play with
it a little early are welcome to check it out and submit bug fixes to
bugzilla:
http://bugzilla.libsdl.org
Cheers!
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.
When you’re updating your projects to use SDL 2.0, you should use sdl2.m4
if you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config
if you’re using the provided shell config script.
I haven’t updated the Visual Studio projects yet, but I will hopefully this
weekend.On Sat, Jan 28, 2012 at 12:42 PM, Sam Lantinga <@slouken> wrote:
So SDL and the recently updated SDL satellite libraries have been updated
to SDL 2.0 in Mercurial:
http://hg.libsdl.orgI haven’t updated the website yet, but those of you who want to play with
it a little early are welcome to check it out and submit bug fixes to
bugzilla:
http://bugzilla.libsdl.orgCheers!
- Sam
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.
Really appreciate that :-).
When you’re updating your projects to use SDL 2.0, you should use sdl2.m4 if
you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config if
you’re using the provided shell config script.
I’m not too happy about sdl2.m4, as we support both SDL 2 and SDL 1.2
in our project. But sdl2.m4 and sdl.m4 can not be used at the same
time, because they both provide the same macro AM_PATH_SDL. I
personally would be happy if this could be changed to AM_PATH_SDL2 in
sdl2.m4, while leaving everything else the same.
I guess even projects that use only SDL 1.2 will face trouble when SDL
2 is also installed and hides/overrides the AM_PATH_SDL macro from
sdl.m4.
Seems the only way around this right now is to use pkg-config instead.
KaiOn Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga wrote:
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.
Very good news indeed.
When you’re updating your projects to use SDL 2.0, you should use sdl2.m4 if
you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config if
you’re using the provided shell config script.
I have a question about this: what are you going to do with Cmake?
Would it be possible to have a updated FindSDL2*.cmake files to be
included in the custom cmake modules until Cmake releases catches up?
Thanks
VittorioOn Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga wrote:
Yep, that’s a good point. Okay, I switched it to AM_PATH_SDL2.
Thanks!On Sun, Jan 29, 2012 at 9:20 AM, Kai Sterker <kai.sterker at gmail.com> wrote:
On Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga <@slouken> wrote:
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.Really appreciate that :-).
When you’re updating your projects to use SDL 2.0, you should use
sdl2.m4 if
you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config
if
you’re using the provided shell config script.I’m not too happy about sdl2.m4, as we support both SDL 2 and SDL 1.2
in our project. But sdl2.m4 and sdl.m4 can not be used at the same
time, because they both provide the same macro AM_PATH_SDL. I
personally would be happy if this could be changed to AM_PATH_SDL2 in
sdl2.m4, while leaving everything else the same.I guess even projects that use only SDL 1.2 will face trouble when SDL
2 is also installed and hides/overrides the AM_PATH_SDL macro from
sdl.m4.Seems the only way around this right now is to use pkg-config instead.
Kai
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
I don’t know much about Cmake. Does it actually include helper functions
to find SDL?
Ryan, can you comment?On Sun, Jan 29, 2012 at 12:48 PM, Vittorio Giovara <vitto.giova at yahoo.it>wrote:
On Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga <@slouken> wrote:
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.Very good news indeed.
When you’re updating your projects to use SDL 2.0, you should use
sdl2.m4 if
you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config
if
you’re using the provided shell config script.I have a question about this: what are you going to do with Cmake?
Would it be possible to have a updated FindSDL2*.cmake files to be
included in the custom cmake modules until Cmake releases catches up?Thanks
Vittorio
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Yes, CMake has modules to find SDL. I overhauled the SDL one a long
time ago and introduced ones for the satellites. There are some minor
bugs I am not happy with in the current SDL module. A SDL2 module
would give us a clean break and also better conform to new packaging
standards adopted by CMake. (The SDL modules predate the standards by
quite a lot.) I haven’t kept up with the new standards though :(On 1/30/12, Sam Lantinga wrote:
I don’t know much about Cmake. Does it actually include helper functions
to find SDL?Ryan, can you comment?
On Sun, Jan 29, 2012 at 12:48 PM, Vittorio Giovara <vitto.giova at yahoo.it>wrote:
On Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga wrote:
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.Very good news indeed.
When you’re updating your projects to use SDL 2.0, you should use
sdl2.m4 if
you’re using autotools, sdl2 if you’re using pkg-config, or sdl2-config
if
you’re using the provided shell config script.I have a question about this: what are you going to do with Cmake?
Would it be possible to have a updated FindSDL2*.cmake files to be
included in the custom cmake modules until Cmake releases catches up?Thanks
Vittorio
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
–
Beginning iPhone Games Development
http://playcontrol.net/iphonegamebook/
One of the nice things about this update is that these should cleanly
install next to the SDL 1.2 versions.
Brilliant.
Go SDL 2!On Sat, Jan 28, 2012 at 6:48 PM, Sam Lantinga wrote: