OpenGL vspkg

Question

OpenGL vspkg

Sid Kraft 101

Rather confused, trying to direct the linker in visual studio, C++ to 64 bit library routines. Direct it to C:\vcpkg\Installed\x64-windows\Lib. The Lib file is labelled OpenGL32??? Sounds like the wrong bit size element to me, please explain

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Rukshan edirisinghe 2,365 Reputation points

2026-11-01T05:46:40+00:00
Hi @Sid Kraft

Good instinct to question it, but the name is misleading here. The "32" in OpenGL32.lib is a historical name, like kernel32.lib and user32.lib. Windows kept these names when it moved to 64-bit, so a 64-bit build still links against files called "...32". A copy sitting under x64-windows\lib (or in the x64 folder of the Windows SDK) is the 64-bit version.

You can confirm it yourself in a few seconds:

Open the Developer Command Prompt for Visual Studio (or x64 Native Tools Command Prompt).

Run dumpbin /headers C:\vcpkg\installed\x64-windows\lib\OpenGL32.lib | findstr machine

If it prints 8664 machine (x64), the library is 64-bit and matches your x64 build. 14C machine (x86) would mean 32-bit.

For the linker settings themselves:

Linker > General > Additional Library Directories: the folder, C:\vcpkg\installed\x64-windows\lib

Linker > Input > Additional Dependencies: only the file name, opengl32.lib

Make sure the project platform is x64, so Visual Studio doesn't mix 32-bit and 64-bit libraries.

Running vcpkg integrate install once also lets Visual Studio find vcpkg's include and lib folders automatically, so you don't need the manual paths. I've also posted details on your related question about the linker error.

Does dumpbin show 8664 for the file?

If this clears up the 32/64-bit confusion, please consider accepting it as the answer. If the build still fails, let me know the exact linker message and I'll be happy to keep helping.

Reference:

https://learn.microsoft.com/en-us/cpp/build/reference/headers

https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/msbuild-integration
JuliaMarvin 23,680 Reputation points Volunteer Moderator

2026-11-01T06:01:48.9666667+00:00

@Rukshan edirisinghe
Please refrain from resurrecting old threads.
See: [Article] Community Tip: Get the most out of active questions

Rukshan edirisinghe 2,365 Reputation points

2026-11-01T05:46:40+00:00

Hi @Sid Kraft

Good instinct to question it, but the name is misleading here. The "32" in OpenGL32.lib is a historical name, like kernel32.lib and user32.lib. Windows kept these names when it moved to 64-bit, so a 64-bit build still links against files called "...32". A copy sitting under x64-windows\lib (or in the x64 folder of the Windows SDK) is the 64-bit version.

You can confirm it yourself in a few seconds:

Open the Developer Command Prompt for Visual Studio (or x64 Native Tools Command Prompt).

Run dumpbin /headers C:\vcpkg\installed\x64-windows\lib\OpenGL32.lib | findstr machine

If it prints 8664 machine (x64), the library is 64-bit and matches your x64 build. 14C machine (x86) would mean 32-bit.

For the linker settings themselves:

Linker > General > Additional Library Directories: the folder, C:\vcpkg\installed\x64-windows\lib

Linker > Input > Additional Dependencies: only the file name, opengl32.lib

Make sure the project platform is x64, so Visual Studio doesn't mix 32-bit and 64-bit libraries.

Running vcpkg integrate install once also lets Visual Studio find vcpkg's include and lib folders automatically, so you don't need the manual paths. I've also posted details on your related question about the linker error.

Does dumpbin show 8664 for the file?

If this clears up the 32/64-bit confusion, please consider accepting it as the answer. If the build still fails, let me know the exact linker message and I'll be happy to keep helping.

Reference:

https://learn.microsoft.com/en-us/cpp/build/reference/headers

https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/msbuild-integration
JuliaMarvin 23,680 Reputation points Volunteer Moderator

2026-11-01T06:01:48.9666667+00:00

@Rukshan edirisinghe
Please refrain from resurrecting old threads.
See: [Article] Community Tip: Get the most out of active questions