What's up with GDC?

[Joerg Joergonson via Digitalmars-d-learn]

On Saturday, 11 June 2016 at 05:12:56 UTC, Mike Parker wrote:
> On Saturday, 11 June 2016 at 04:20:38 UTC, Joerg Joergonson 
> wrote:
>> On Saturday, 11 June 2016 at 01:43:21 UTC, Adam D. Ruppe wrote:
>
>>> What's the exact message and what did you do? The 
>>> opengl32.lib I have on my github is for dmd 32 bit, ldc uses 
>>> the Microsoft one I think so you shouldn't need anything else.
>>
>> It just says the format is invalid. I used the one you 
>> supplied in the package and never worried about it. I'll try 
>> some other libs when I get a chance.
>>
>
> OpenGL32.lib and glu32.lib are part of the Windows SDK. 
> Assuming you've got VS 2015 installed, they should be part of 
> the installation and should be available out of the box. Adam's 
> lib is solely for use with OPTLINK when compiling with DMD 
> using the default -m32 on Windows, since DMD does not ship with 
> the opengl lib. When compiling with -m32mscoff or -m64, it will 
> use Visual Studios libraries.

That's not true unless I'm not suppose to import them directly. 
When I switch to 64-bit build I get same errors. Basically only 
dmd x86 works.

It could be my setup.

This is EXACTLY what anyone who is doing this sort of stuff needs 
to know:

1. How to tell the difference between different libs and what 
kind of libs are required for what kind of compiler and build.

       x86    x64
DMD    .      .
LDC    .      .
GDC    .      .

Please fill in the table for windows, linux, etc.

If I know this information then it is at least easy to make sure 
I have matching socks. Else it's kinda pointless to put on shoes?


2. How does the D build system fetch the libs? It uses the 
sci.ini path? What about Visual D?

Just because I have the correct stuff from 1 doesn't mean it is 
in the "correct" place.

Where does D look for these? I assume in the "libs" directory?
    pragma(lib, "opengl32");
    pragma(lib, "glu32");

3. How to get different compilers and versions to play along? I 
would eventually like to build for win/lin/osx for both x64 and 
x86.

Without these 3 ingredients, everything is futile!


I am using Visual D, BTW. It seems to have a lot of stuff setup 
by default but I haven't went in and messed with the settings 
much.