VSCode IntelliSense with JUCE

General JUCE discussion
1

Does anyone have a settings.json and/or c_cpp_properties.json to share that clears up all the noisy squiggles in VSCode’s C++ Intellisense?

The code always looks fine in Xcode or VS but it’d be really cool for unnecessary error squiggles to go away like:
ValueTree is not a class or struct name
or
namespace juce has no member "Graphics.

Right now, I try to keep my includePaths to just my source, the JuceLibraryCode and the JUCE modules… so like

includePaths: [
"${workspaceFolder}/myProject/Source",
"${workspaceFolder}/myProject/JuceLibraryCode",
"${workspaceFolder}/JUCE/modules",

"${workspaceFolder}/myProject/Source/**",
"${workspaceFolder}/myProject/JuceLibraryCode/**",
"${workspaceFolder}/JUCE/modules/**",
]

Anyone have any luck with this or is it best to just ignore this stuff?

2

We use the following includePaths for our Project in VSCode and it works for us (JUCE modules are inside the JuceLibraryCode directory):

"includePath": [
    "${workspaceFolder}/JuceLibraryCode/**",
    "${workspaceFolder}/Source/**",
    "${workspaceFolder}/Plugins/**",
    "${workspaceFolder}/TestHelpers/**"
]
3

There is also forcedIncludes if things get really dire. Alternatively, if you’re using cmake, you can throw all the settings out the window and let the cmaketools extension do it for you.

4

Thanks!
I go back and forth between the C++ extension and CMake Tools. CMake Tools has a weird issue where it complains about dependencies in the Accelerate Framework (cblas.h) and but if I use C++ and explicitly include the path to fix that cblas.h issue, then it complains about JUCE stuff. I keep going back and forth.
But @ad-oe, it’s good to hear you’ve had luck with the simple includePaths. It gives me some hope that maybe I can get things working on my side also if I spend a little more time with it.

5

JUCE modules often include a set of cpp files using #include in the main module cpp file(s). When you’re working with one of those included cpp files, IntelliSense may be unaware that the file is actually included by a larger file which pulls in those squiggly dependencies.

To resolve that, I’ve ended up putting the main module as an include for each individual source file. During actual compilation, they are harmlessly excluded by your usual #ifdef or “pragma once” shields. But when you’re working on that source file with IntelliSense, it will know to include those header dependencies.

2 Likes