Follow the tracker
You can find a set of known issues and feature requests in our tracker. Some issues in the AppCode tracker are also applicable to the CLion EAP build.
What are the most important and known issues and limitations?
- Toolchain changes in settings do not affect the project automatically, call the Reload CMake Project action via CMake tool window or by action name to apply changes.
- CMakeCache changes should be applied via Apply Changes and Reload button in the tool window.
- Most compiler errors are not highlighted in the editor.
- CLion doesn’t update CMakeLists.txt automatically when adding new file to the project.
- CLion's new file wizard doesn't support C++ class templates.
Compilers, CMake and language standards limitations
- CLion supports only GNU toolchain, that means only GCC and Clang compilers on Linux and OS X, and MinGW (version 3.2 only, 64-bit version is not supported yet) and Cygwin toolchains on Windows.
Note: If you are using Visual Studio for C++ development (and Visual C++ Compiler), try our ReSharper for C++.
- CLion supports only the following C and C++ standards: C99, C++03, C++11.
- C++11 user-defined literals are not supported.
- C++11 сonstexpr expressions (OC-10355, CPP-396) and enum classes (OC-9129) are not fully supported.
- CMake 3 is not yet supported.
- Environment variables and parameters can't be passed to the CMake command (CPP-188). Write them in CMakeLists.txt files directly or set in CMakeCache. To add parameter to CMakeCache use this workaround until we fix an issue with adding custom parameters to Cache from the IDE.
Performance and memory
- On the large code bases (especially when using Boost) performance and memory issues during indexing and editing are possible (increasing memory may help).
- Some issues are possible when debugging 32-bit projects with 64-bit GDB.