The SDL forums have moved to discourse.libsdl.org.
This is just a read-only archive of the previous forums, to keep old links working.

I'm trying to build the latest SDL 1.3 code on MinGW, and it seems that the changes that were added as part of changeset 4763 (518d1679d2d0) have added the include "msctf.h" into SDL_win32video.h - When building in MinGW, I now get an error saying that this header is not present. What is it part of?

Is there a current "recommended" revision number in the repository that people would suggest using, that isn't the latest version?

No, that would be counterproductive. "[r]ecommended revisions"? It is
preferable to read about and fix a new bug.

Programmers don't want to experience the same grief time travelers do.



On Thu, Sep 9, 2010 at 10:00 AM, thatbloke wrote:
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Ok, so... got any insight as to what this header is part of?

The "ms" in the file name should give you a hint.  Have you installed all the pertinent SDKs (I personally don't know which are needed)?  Have you Googled at all?

Jonny D


On Thu, Sep 9, 2010 at 11:20 AM, thatbloke wrote:

On my machine, "msctf.h" is located in C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include
Its part of the platform SDK.

On Thu, Sep 9, 2010 at 11:20 AM, thatbloke wrote:

I am running into the same issue. I copied over msctf.h from the MS SDK into my mingw installation, recompiled, got more missing file errors, copied those over as well. Finally I ran into a compile error with "sdl_win32video: error expected specifier qualifier list before compositionform"

@thatbloke: if you're looking for a "recommended" revision, it would probably be the tarball listed on the SDL website under SDL 1.3. It's a bit outdated (August) but I managed to get it to compile successfully. Hey, it must be on the main website for a reason right?

I realise that the "MS" is probably a clue - it seems that it is indeed part of the platform SDK - but that then leads me to wonder if it's an issue with MinGW, or if there is now an incompatibility with regard to building SDL on the MinGW platform. I would not expect that the Microsoft Platform SDK will work in conjunction with the MinGW compiler.

In addition, I have the tarball on the "Get SDL" page, but from what I can tell there is potentially some issue with fullscreen mode that was fixed in a later version (which is precisely what I need, plus I need the ability to display stuff on a second display).

Why?
MinGW works fine with Microsoft .lib files. How else would it
function, if not by using the ms libraries?



On Mon, Sep 13, 2010 at 4:35 AM, thatbloke wrote:
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Yes, but there are a lot of problems with using MS header files. MS C++ code has always been a bit non-standards complaint and a lot of times you can't simply drag files over to MinGW as a drop-in-replacement. This is why MinGW provides a lot of its own header files for the win32 api.

Have you tried compiling SDL 1.3 yourself? If so can you give us instructions on how you set up your build environment?

Compiling SDL 1.3 using VS 2010 was no go either, kept getting linker errors with functions in Version.lib, which is in default library search path.


I am currently running into this problem as well.

Jeremiah wrote:
This is how it would function (and usually does function for the core API):
http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/RuntimeLibrary/Win32-API/w32api-3.15/w32api-3.15-1-mingw32-src.tar.lzma/download

which is not released by Microsoft.
The mingw linker handles most MSVC produced lib files ok (for a "long"
while now), but this wasn't always the case. Basic support for C++
libraries was even more recent, IIRC.

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Well ofcourse mingw source code isn't released by Microsoft, .

MingW doesn't "need" windows from a technical standpoint . But without
it, it would have no purpose. I misspoke when I said function.
Function should be replaced with a different word.
But at least the OP gets the overall message.
Yes, SDL has dependencies.
Yes, they all can work through mingw.



On Thu, Sep 16, 2010 at 1:51 PM, John K. Luebs wrote:
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Jeremiah wrote:
But this was not about source code for mingw, and that is not what I
linked to. I linked to an independent (non-MS) SDK header/library
package that has been used as part of mingw for years.
The poster mentioned about not expecting the Platform SDK to not work
with mingw. As it turns out, for a long while, mingw would certainly not
work with most of the Platform SDK for a number of reasons.

There was a time when GNU binutils would not work with MS style lib
library files at all.

And even now, many existing Windows applications can be built just fine
without the Platform SDK, because many parts of it exist in no MS
implementations.

I'm not talking about runtime environment, but rather build environment.
These days, most Windows applications I need to build, I build just fine
in a cross-compilation environment on Linux and do not use any MS
Platform SDK/MS lib files or MS distributed stuff (as far as I know),
and that's all I was commenting on.

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

This is for the IME support in SDL 1.3. Daniel, do you know how this
would be compiled on MinGW?

On Thu, Sep 9, 2010 at 7:00 AM, thatbloke wrote:



--
    -Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Ah, I forgot about this.
I knew from the start that MinGW didn't have a msctf.h header.
I'll have to figure something out.
I may just have to write my own header for the portion of the TSF that I use.
MinGW has the required libs, just not all the headers.
I'll start work on this right away.

Okay, I've managed to compile SDL 1.3 in MinGW.
However, it won't link since the IIDs and CLSIDs I use aren't in libuuid.a.
I'll have to see what I can do about this.

Okay, I've compiled, linked, and lightly tested it (on XP, need to test on 7).
I had to do the following:
1) Copy msctf.h, TextStor.h, ctfutb.h, and Rpcsal.h to your include directory.
2) Add this to msctf.h (after the other includes):

3) Add this to EXTRA_LDFLAGS in the makefile:

4) Add this to SDL_win32video.h:

5) Add this to SDL_win32keyboard.c:


I _think_ that's all.
Obviously this is a temporary solution, I'll have to talk to sam about a more permanent solution.
But for now, that should get things working.

A workaround is in place now.
Everything should be fine.

I also added a bug report to the MinGW tracker for the missing headers and CLSIDs/IIDs.

Thanks Daniel!

On Sun, Sep 19, 2010 at 9:03 PM, dewyatt wrote:



--
    -Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Hi guys, Thanks for the work you have put in on this, thought I would let you know that the latest SDL code in Mercurial just compiled flawlessly on my MinGW environment. (32-bit, using Vista).

Thanks!

Great!

On Wed, Sep 22, 2010 at 6:02 AM, thatbloke wrote:



--
    -Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

I'm afraid I am running into this same problem with compiling SDL 1.3 under Windows 7 with VC2005.

I have the latest .net SDK installed, DirectX SDK (June 2010). Am I missing one?

Yes - the Platform SDK.
http://msdn.microsoft.com/en-us/windows/bb980924.aspx

On 12/16/10 1:37 AM, ebyard wrote: