[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Xerces library problem

From: tek
Subject: Re: [Mingw-cross-env-list] Xerces library problem
Date: Tue, 13 Jul 2010 16:07:09 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20100619 Icedove/3.0.5

On 07/13/2010 01:52 PM, Volker Grabsch wrote:
tek<address@hidden>  schrieb:
On 07/12/2010 02:22 PM, Volker Grabsch wrote:
Note that we don't have that issue in Mingw-cross-env. More general,
that issue shouldn't be present in any recent MinGW system.

I did not post here for my OpenGL issues, essentially because I did not
investigate it enough already and I guess mingw-cross-env is not
concerned about it since it doesn't seem to be mentioned anywhere.
Now for the details of cross-compiling it: at link time, I have some
undefined references related to shader calls only (like glUseProgram()
etc...). Besides of that, all other OpenGL calls do not seem to be a
Please provide a minimal test program that reproduces the error.

That's precisely what I am doing now. But investigating my OpenGL issues on the web, I've seen that things get a bit more complicated when compiling for Windows if you use GL extensions.

I'm not surprised at all. I'm in the video game industry and I knew that Microsoft decided not to support OpenGL since... 15 years (well, roughly since DirectX came out). We cannot completely blame them for that after all, but I just did not realize during all these years how much it has hit the GL community in the game industry (M$ won a battle here).

Result: while under Linux, you can easily use all OpenGL extensions by simply including <glext.h>, under Windows, you have to use some 3rd party libraries (like GLee or GLew, fortunately free) to sort it out without manually requesting OpenGL for those extensions functions after functions (which is very annoying).

Out of the game industry, I guess most people only use the robust parts of OpenGL (<= 1.1, that's what you get on Windows today, back to 1995). And that part is precisely what my cross-compiler/linker did not complain about. The rest is just a sad battlefield...

Well, now I'm out of the subject with all this boring business non-sense. I would be glad to help people there (as you help me), but I think GL extensions is of very little interest to anyone around here. The issues I talk about seems widely covered on the web. I'm currently on it and I guess the best I could do is providing a link to what I decided to focus:


Maybe someone on this list likes to try to make it run, which is
sometimes a funny excercise.

Even if we aren't able to help you, creating a minimal program
is never wasted time. You'll have to provide it when you ask at
other places, too. And you'll learn more about the problem by
creating it.

(Sometimes preparing the minimal program is enough for me to
  see where the error occurs, and to fix it without having to
  ask for help anymore.)

As I promised, once I resolve my Xerces issue, I'll let you know what was wrong.

I focused back on OpenGL recently essentially to make sure I have to sort it out alone (and it seems to be the case). But please, don't take it wrong: if you insist, it would be a pleasure for me to report here what I did to resolve it too. I just came to the conclusion that it is not the right place to share about OpenGL extensions, just because it is already covered on the web. Maybe I'm wrong... just let me know :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]