This page lists various community-contributed plugins for different editors. Note that none of these plugins are officially supported, but some users have reported good experiences.
Follow the Compilation Database instructions below to create the appropriate project description file in the fuchsia root directory.
Then in CLion choose Import Project from Sources and select the fuchsia root directory.
To improve performance you can try some or all of the following. They are only suggestions, we recommend checking with directly with JetBrains at https://intellij-support.jetbrains.com/hc to be sure what works best for your environment.
To speed up indexing time you can exclude directories you are not working with. You can do that in the Project View by right-clicking each directory and choosing Mark directory as->Excluded. Note the affected configuration is stored in <project>/.idea/misc.xml
See Control Source, Library, and Exclude Directories - Help | CLion for more information.
The fuchsia source tree has a fair number of git repositories. Scanning them can use CPU cycles for CLion. You can unregister the git repositories you are not working on under File -> Settings -> Version Control. They will still be listed there so you can add them back later if needed.
See Tuning CLion - Help | CLion for general tips on tweaking CLion JVM Options and Platform Properties. As that link suggests, contact CLion support for instructions regarding the options and values that might help you with whatever issue you are trying to solve.
A Compilation Database file, compile_commands.json
, will be created automatically by fx
within your current build directory as well as automatically symlinked to your source root.
Note that this file is only intended to help the IDE find and parse the source files. Building should still be done with fx build
.
Note: There is an ongoing issue where CLion shows compiler errors for a few hundred files in the Fuchsia source code. Other files should work fine in CLion.
See Helpful Vim tools for Fuchsia development.
See more VS Code configuration recommendations for Fuchsia contributors.
Install vscode-clangd. Disable the default C/C++ extension if you have it installed.
If you don‘t have clangd
available in your environment (that is, included in $PATH
), or if you want to ensure that you use the same version of clangd
that is used by the Fuchsia toolchain, update VS Code’s settings.json
file to set the path to clangd
as follows:
Note: The path to FUCHSIA_CHECKOUT_ROOT_DIRECTORY
below needs to be an absolute path.
"clangd.path": "<FUCHSIA_CHECKOUT_ROOT_DIRECTORY>/prebuilt/third_party/clang/<PLATFORM>/bin/clangd",
After updating the settings.json
file, you need to restart VS Code.
You may also benefit from enabling background indexing and clang-tidy using the following settings:
"clangd.arguments": [ "--clang-tidy", "--background-index" ]
Further details on clangd setup can be found here.