CODEWITHSUNDEEP
c++cmakeclion
paulgessinger
paulgessinger

Reputation: 163

Tell CLion to use header include path with prefix

I have a project layout as follows:

I cannot change the directory layout due to the build system that we're using. Headers are included as

#include "project_a/some_header.h

also from the corresponding .cxx file. I've created a CMakeLists.txt file in the root directory, that adds all my projects via include_directories(project_a project_b), which should be the path prefixed before the one given in the #include. CLion does not manage to find and index any of my files.

Additionally, I have an automatically generated directory of headers of structure

and I've set them up accordingly, but it also does not work.

Does CLion not manage to resolve the prefixed path in the #include or why is this not working?

Upvotes: 4

Views: 8733

Answers (2)

PolyGlot
PolyGlot

Reputation: 790

In CMakeList.txt, which should be located in parent folder, "workspace" folder in that situation, add

set(INCLUDE_DIRECTORIES ./)

If, for example, there is a parent folder, that holds include files:

  • workspace
    • includes_folder
      • project_a
        • a.h
    • b.h: #include <project_a/a.h>

Then CMakeList.txt should contain

set(INCLUDE_DIRECTORIES ./)
include_directories(includes_folder)

Upvotes: 3

Thomas Steinholz
Thomas Steinholz

Reputation: 88

If the only thing that doesn't work is Clion's interpretation of your headers then you should check out the Clion FAQ. If Clion's not working the way you expect then your CMake project might not be set up correctly or you might be doing something unintentionally. You should show us your CMakeLists.txt.

From the Clion FAQ:

Q: CLion fails to find some of my headers. Where does it search for them? A: CLion searches through the same places CMake does. Set the INCLUDE_DIRECTORIES variable in CMake to provide the headers path to the IDE.

By the way, in this wiki you can find a lot of useful CMake variables with descriptions that can be especially helpful if you are new to CMake.

Q: Refactorings are not working and highlighting is wrong, even though the project can be compiled correctly. What’s happened? A: Most probably CLion is unaware of some files in your project (these files are grayed out in the project tree): non-project-files It gets this information from the CMakeLists.txt files in the following way: set(SOURCE_FILES main.cpp) add_executable(my_exec ${SOURCE_FILES}) This is how CLion now knows that main.cpp is included in your project. As for now, header files (in case their names differ from the appropriate .cpp files already added to the SOURCE_FILES variable) should also be included in the project in that way.

Upvotes: 0

Related Questions