Rather than setting the compiler and linker flags directly, you should use the âHeader Search Pathsâ and âExtra Library Search Pathsâ fields, which can be found in the settings pane for each build configuration (i.e. the âDebugâ/âReleaseâ list entries on the left side of the Projucer window).
If youâre linking against a staticlib, the windows runtime must match between the staticlib and whatever itâs being linked to. That means, if the staticlib was built against the dynamic runtime, then your JUCE target should build against the dynamic runtime too. If the staticlib was built against the static runtime, then the JUCE target should use the static runtime. I think in newer versions of VS you should see linker errors if the runtime libraries donât match.
It looks correctly formatted. My best guess is that the relative path is resolving to an unexpected location. I think that paths are resolved relative to the Builds/VisualStudio2019 folder.