I have a CLion C++ project that has the following structure:
| ----> my_own.hpp
You need to create a
CMakeLists.txt for CLion to be happy. It is enough to declare all the source files, you don't have to convert your scons (or any other build system) to cmake.
You don't even have to write the CMakeLists.txt by hand, you can ask CLion to do it:
File | Import project ... | and then point at the directory containing your project.
Now edit the generated
CMakeLists.txt and add a cmake command to tell CLion where to find the includes (actually to tell the compiler, and CLion will reuse that information).
Since your source files use the include as
#include "my_includes/my_own.hpp", you need to tell cmake the base directory containing directory
Where the dot means the same directory as the one containing the
I tested with a project reproducing your layout and from
my_src.cpp I can navigate to
Then to build you still have to use scons in a console. It is also possible to add a cmake command,
add_custom_target() that will call your scons (or your make, or whatever), so that you can also navigate from CLion to the build errors.