Jump to content

View more

Image of the Day

Adding some finishing touches...
Follow us for more
#screenshotsaturday #indiedev... by #MakeGoodGames https://t.co/Otbwywbm3a
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

Sign up now

Build issues with CL and GLFW

4: Adsense
  • You cannot reply to this topic
2 replies to this topic

#1 NielsBross   Members   


Posted 17 April 2017 - 08:45 AM

Hey everyone.

I've recently tried to move from compiling my engine with g++ to cl (Microsoft's compiler) from Visual Studio 2015, but I've run into some issues.

So basically, we want to compile for 64bit thus initializing CL with

vcvarsall.bat x64

This means we want 64 bit version of every library we are using. We are using OpenGL with GLFW3 and GLAD for loading. Beyond that we are using OpenAL and FreeType 2.7.

Before I get into any more detail I wanted to know if anyone had experience with CL using those two libraries, and maybe could share what they did to make it link without errors.

We are basically having issues with the linking to the correct libraries.

So the question is really, if you have any experience with CL and at least some of those libraries while compiling for 64bit from the command line, do you have any experiences (both good and bad) that could help, and more specifically, which versions and links you used for the libraries or which you built yourself and so on.

Hope someone can help :)

I can clear things up about the specific build file if anyone wants, but for now I'll just leave it as is.

#2 vstrakh   Members   


Posted 17 April 2017 - 12:45 PM

Is there something that doesn't allow you to build your project using visual studio's projects/solution files? It just might be faster to create a solution with projects for all the libs you want linked statically. You will have those libs automatically rebuilt in whatever settings your main project require. It worked for me, including freetype and other opensource libs.

#3 NielsBross   Members   


Posted 17 April 2017 - 12:58 PM

Thanks for the reply!

Yeah, we considered that, but I think we just didn't really need to use Visual Studio and felt it was enough to use the compiler (and seemingly faster).

We did fix the issue in the end though and found out it was mostly a chicken and egg thing with how we compiled some dll's.