contributing/development/configuring_an_ide/clion

[giscus[bot]]

contributing/development/configuring_an_ide/clion

CLion is a commercial JetBrains IDE for C++. Importing the project: CLion can import a project's compilation database file, commonly named compile_commands.json. To generate the compilation databas...

https://docs.godotengine.org/en/stable/contributing/development/configuring_an_ide/clion.html

[ajpgarner]

Using CLion 2023.3.4 on Windows 10, I found it necessary to explicitly choose specifically the .console.exe version of the editor, as otherwise I had the aforementioned issue of it only being possible to debug the Godot Project Manager window.

[nmerget]

Using CLion 2024.2.1 on Windows 11, to enable the debugger I had to go to Settings -> Build, Execution, Deployment -> Toolchain: Select MinGW (Default) and move it down, to makeVisual Studio the default.

Otherwise I got the error at all breakpoints: The breakpoint will not currently be hit. No executable code is associated with this line

[voxelv]

This didn't fix it for me. The problem I had was that I selected the wrong executable.
I had selected
godot.windows.editor.x86_64.exe
but I should have selected
godot.windows.editor.dev.x86_64.exe
(Note the dev in the second one)

[Nodragem]

On my side, I get a warning This file does not belong to any project target, code insight features might not work, any ideas how to fix it? I think I need it to clean my #include list.

[nmerget]

Three things I found out (for windows):

1. I had to do was to add cl to my PATH like this.

2. You need to run scons compiledb=yes test=yes if you want to add all files inside tests directories into the compile_commands.json.

3. If you create a new file you need to run scons compiledb=yes again. Maybe you can copy paste a block from compile_commands.json and just change the path, but anywas you need to build the .obj file via scons