0
I'm currently making an OpenGL application in Visual Studio 2015, and have successfully linked and included all my things for GLFW, GLEW, etc.
However when I run my application, I need to include glew32.dll
, no problem at all. I just go and grab the x64 dll and add it to the project folder. However now when I run my program in 32-bit mode, it breaks, and vice-versa if I was to use the 32-bit dll on a 64-bit program. The only cheap fix to this is to include the architecture specific dll's to the build folders.
Is there a way I can include the dll's on an architecture-specific basis, because I want to house my resulting program in a form such as:
Program Directory
- game.exe
- game_x64.exe
- x64 (folder)
- glew32.dll
- x32 (folder)
- glew32.dll
If something like this isn't possible, I'm more than happy to have a glew32.dll
and glew32_x64.dll
housed in the one folder instead, but that'll probably never happen due to the library not looking for the new dll...
My guess is this should be over at stackoverflow. If you're already doing multiple builds (one for x32 and one for x64) shouldn't it be possible to include the linkage of that DLL in either build configuration?
– Seth – 2016-09-21T08:30:15.663@Seth I was thinking of SO too, but realised that it isn't really a programming question (unless it is :O) but rather a question on how to get VS to do it for me. As for the linkage, I can't find any options. I link the include headers, then the
.lib
locations, and the.lib
names; thats about it. No.dll
specification. :O – None – 2016-09-21T08:33:51.553What language are you using? Either of those links might help if it is C#: Link1 Link2 This KB Might help to understand who it's looking for DLLs and how to adjust the code?
– Seth – 2016-09-21T08:53:17.593@Seth Sorry Seth, I'm using C++. – None – 2016-09-21T08:56:54.937
1It’s x86, by the way. x32 is only used for Linux’ x32 ABI. – Daniel B – 2016-09-21T10:22:45.320