Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GLEW Linker Warning 4217 #9

Open
EfficientJava opened this issue Jul 18, 2024 · 0 comments
Open

GLEW Linker Warning 4217 #9

EfficientJava opened this issue Jul 18, 2024 · 0 comments

Comments

@EfficientJava
Copy link

Hey so I followed alongside your How to Properly Setup C++ Projects video and used this template. I included GLFW and GLEW into the Core project (as much of the core engine is using these libraries), and I linked the two libraries in the Editor and Runtime projects. The result is a working game engine, but the console is spammed with a bunch of link warning 4217. I'm not one to disable warnings, but the project is running smoothly. After some research I've come to the conclusion that since the Core project (a static library) is including the header files of GLEW and GLFW but not the implementations, when the compiler tries to replace all the function calls from GLEW or GLFW in the Core project files, they're using symbol names (such as "__glewAttachShader") instead of their corresponding function names which get replaced in the Editor and Runtime projects. Is there a work-around to this? Or a way to fix these warnings?
Here's an example of a full warning:
LINK : warning LNK4217: symbol '__glewAttachShader' defined in 'glew32s.lib(glew.obj)' is imported by 'Main.obj' in function 'main'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant