Custom modules in CMake and CLion code insights

CMake
1

I’m moving a JUCE 7 Projucer + Xcode project to building with CMake in CLion. Everything builds nicely but I can’t get CLion to include any of my custom modules in its code insights.

In other words none of the ‘Go to declaration’ type functions work as it simply seems to know nothing about the classes in my custom modules (or the juce modules either).

I’ve tried changing the CLion project root but that was already set correctly.

I’m including the modules using:

juce_add_modules(
        ALIAS_NAMESPACE poly
        poly_core
        poly_dsp
        poly_ui
        poly_test)

Which itself is added using a standard cmake add_subdirectory(Modules) command.

All the source files in CLion have a “This file does not belong to any project target; code insights feature may not work properly” banner displayed at the top.

Screenshot 2024-09-27 at 20.29.51
Screenshot 2024-09-27 at 20.29.511720×170 22.2 KB

Are there any specific cmake settings that need to be enabled for CLion to see the module source files?

2

After removing boost as a dependency this is working now. I think CLion was unable to index the project fully due to the sheer size of the boost repo.