First, codelite searches for an updated compile_commands.json file after the build is over (does not matter if it succeeded or not).
So make sure:
- You have a workspace opened in codelite with all your sources
- Your workspace file (.workspace file) should be on the same directory as the top level CMakeLists.txt file
- Issue a build (I assume its a custom build project that simply invoke 'make' or something similar)
- When the build is done, codelite will pick the compile_commands.json file and will update its 'compilation.db' (located under workspace-path/.codelite/compilation.db)
To confirm that it worked, you can:
- Open the file workspace-path/.codelite/compilation.db (using the DbExplorer plugin and view its content, located under in the workspace view at the far right...)
- Increase codelite's logging from: settings->global editor preferences->misc->log, and change the verbosity to 'Debug', open the file '~/.codelite/codelite.log' or %appdata%\codelite\codelite.log
Last but not least:
Its your first post on the forum, so please make sure you have read the 'HOW TO POST' thread (check my signature) - you need to provide more information
To configure your workspace properly to use your CMake build, see here:
http://codelite.org/LiteEditor/CustomMakefiles#toc3
Eran