I was hoping someone can provide some kind of a tip to fix the error: ‘base/source/baseiids.cpp’ file not found, which I get when compiling the audio plugin host example (on Windows 10 64bit). The error remains after checking:
The VST SDK path is set correctly (the path is not turning to red text)
Resaving the project after setting the VST SDK path
I tried VST SDK 366 and 367
Enabling VST3 only in the juce_audio_processors component
The most important info would be, which version of ProJucer…? If it is before a certain timepoint (somewhere in 4.3.1 in develop, and definitely in master before that), than it will work with VST <= 3.6.5, otherwise with >=3.6.7 (3.6.6 IIRC was an unlucky on, you might want to avoid).
I’ve been getting the same error. Currently running MacOS Sierra, Projucer 5, Xcode 8.3.2. Most recent Steinberg SDK has been downloaded and placed. My build fails in Xcode and Projucer and states ‘base/source/baseiids.cpp’ file not found. But it is clearly there. I would definitely consider myself a beginner in this realm but feel I’m missing something pretty basic. Any thoughts/words are welcome!
Placing the SDK in the JUCE directory will only solve this problem if the JUCE directory is in the compiler include search paths.
Put the SDK somewhere more convenient and add the path to it to your Projucer project. You can do this via the Projucer -> Preferences -> Paths menu or, for a specific exporter configuration or the live build, adding it to the “Header search paths” field (accessible by clicking on the gear icon for the live build).
Yes - if you read the previous posts then all the info is there, though it might be scattered around a bit.
In short: if you’re seeing ‘base/source/baseiids.cpp’ file not found, then you need to add the path to the VST3 SDK to the header include paths of the exporter you’re using or, if you’re using the live build, the live build settings.
We’ve tried adding a big comment in the source file above that include statement that explains what you need to do, but frustratingly people don’t seem to ever bother actually looking at the line of code where the error happened, they just read the error text and come on here to ask about it…
However, there’s a new C++ trick in the latest compilers called __has_include which we might be able to use to throw up our own special error message when people fail to a particular header file available, and that might help to avoid some confusion! We’ll investigate that at some point.
After adding “~/SDKs/VST3 SDK” to the live build settings under “System header paths” the live building system works.
Thank you very much for your help!
PS: I suppose that the examples should work out of the box. Therefore the exporter settings and the Projucer live build system probably should use the path defined under “Projucer > Preferences > Paths > VST3 SDK” by default. The first works, the second not, so this probably is a bug. Is there a bug tracker where I should post this - or is this message enough?
I actually did that already (as I tried to describe in my first posting) - but it didn’t work. The solution was to add the path under the live build settings under “System header paths” as described by Tom in the next posting.