Telling VS2019 linker where library dependencies live

#1

I‘m developing my plugins on macOS, and now it’s time to make them compile on Windows!
I have a library as dependency. In the XCode exporter, I add -L/usr/local/lib to tell the linker where the .lib file is located, but that doesn’t work with the VS 2019 exporter.

So what’s the best way to tell Visual Studio where to look for dependency .lib files?
I’d prefer a solution based on a Projucer setting, although I’ve read I could also add a #pragma.

I‘m a real noob when it comes to Windows, so please excuse the basic question, but I couldn’t find anything definitive here in the forums.

Thanks in advance!

#2

Set the “Extra Library Search Paths” in the Projucer.

39%20AM
Screen Shot 2019-08-15 at 9.14.39 AM.jpg1640×834 161 KB

Hope that helps-

Matt

1 Like
#3

What I also saw was, that VS expects the name.lib, so if the file was:
libavformat.lib I put in avformat.lib in extra libraries to link. Maybe that’s the culprit

1 Like
#4

Wow, that’s indeed what tripped me up, especially cause the tooltip in the projucer says these entries shouldn’t contain any platform-specific extensions. Thanks!