I saw last weekend what you said to me(windib uses standard events of win32/win64).
Also, I was testing directx backend on win64 and I tried to fix the dinput initialization error but I could not do it, the problem is on somewhere between dinput (version 5.0) and win64, so, finally, I discarded directx backend on Win64 to use windib. Right now, I will test glSDL…hope this works fine!
I now what you mean…there is not too much Win64+64bits programming information out there… I have downloaded a lot of AMD documents and some tips but they are very old. If I can, I will include in my web all problems that I found porting my library to 64bits code and compiling SDL,SMPEG,SDL_net,SDL_mixer,UCL and TinyXML and how to fix them. I have to say that these libraries are well done and dont need more than a couple of changes(lucky!).
Ryan, if you (and the SDL community) is interested on it, I could send you the SDL binary compiled for Win64 on 64bits native code.
Thanks a lot for you replies
---- “Ryan C. Gordon” escribi?:
My target is to use glSDL so directx code is not important for me, my question is…what happened with the events control? If I use windib…who manages the events?
WinDib does…I might be misunderstanding your question. In the DirectX
code, it uses DirectInput to get mouse and keyboard events; in the
WinDib code, it uses standard Win32/Win64 event loop, which won’t be
going away, or every existing Windows program would break.
I don’t know where glSDL gets its events from, but if it’s built on the
existing platform code (windib/glx/etc), you should be fine.
On the other hand…Any web/docs/forums with 64bits information?
I’m not aware of one…usually you have to shuffle through Powerpoint
presentations from various AMD and Microsoft events if you want Win64
development tips…anyone know any good resources for this?
SDL mailing list
SDL at libsdl.org