[Answered] SFML 2.2 and 64 bit opengl32

[thecheeselover]

I've built SFML 2.2 for multiple 64 bit compilers but I just noticed that it links opengl32. By default, opengl32 is a 32 bit dll. First of, does it mean I need to put the shared library in my bin folder or linking statically SFML fixes that? Also, in the cmake files, sfml only links openl32 and doesn't try to get the 64 bit opengl32 located at %ProgramFiles%\Microsoft SDKs\Windows\<version>\Lib\x64\OpenGL32.lib. This means that the .lib files, that are actually multiple .o files, uses a 32 bit library. Does it actually change anything or it only matters in an executable?

Thanks in advance!

[eXpl0it3r]

opengl32 is a system library, you don't have to think about whether it's 32-bit or 64-bit or where it's located, just make sure it gets linked into SFML (or if you link statically, linked into your application).

I hope you understand that just because it has a "32" at the end, doesn't automatically mean it's a 32-bit library.
Also opengl32 is usually provided by the graphics driver, so they may differ an any system and you should not try to ship it with your application.

[thecheeselover]

I hope you understand that just because it has a "32" at the end, doesn't automatically mean it's a 32-bit library.

I understand that because actually the 64 bit version of opengl32 is called opengl32.

you don't have to think about whether it's 32-bit or 64-bit

Why is that so? When building a 64 bit application, linking 32 bit libraries either won't work or will drastically decrease the performance due to "casting" (I forgot the real term). If you say the truth (not that I doubt you, it's just that I'm really confused), then do I actually need to link opengl32 in my final application if I do 3D?

Thanks for your answer!

[eXpl0it3r]

The reason you don't have to think about is, that by choosing the right compiler toolchain (32 bit vs 64 bit) you'll link against the right version.