Qt projects

1. Add the find_package command to locate the required libraries and header files. For example:

   find_package(Qt5Widgets REQUIRED)

   Then, use target_link_libraries to make your target dependent on these libraries and headers:

   target_link_libraries(helloworld Qt5::Widgets)

2. For find_package to perform successfully, CMake should be instructed on where to find the Qt installation.

   One of the ways to do this is by setting the CMAKE_PREFIX_PATH variable. You can either pass it via -D in the CMake settings dialog or via the set command before find_package.

   For example, in the case of MinGW on Windows:

   set(CMAKE_PREFIX_PATH "C:\\Qt\\Qt5.14.0\\5.14.0\\mingw73_32\\")

   or

   set(CMAKE_PREFIX_PATH "C:\\Qt\\Qt5.14.0\\5.14.0\\mingw73_32\\lib\\cmake\\")

3. If your project uses MOC, UIC, or RCC, add the following lines to enable automatic invocation of the corresponding compilers:

   set(CMAKE_AUTOMOC ON)
   set(CMAKE_AUTOUIC ON)
   set(CMAKE_AUTORCC ON)

4. List all the .ui and .qrc files in the add_executable() command along with your .cpp sources:

   add_executable(
       helloworld
       main.cpp mainwindow.cpp
       application.qrc
   )

1. When installing Qt on Windows, pick the distributive that matches the environment you are using in CLion, MinGW or MSVC.

   For MinGW, both the version and the bitness (32-bit MinGW or MinGW-w64) should match with your toolchain setup.

   

2. In CLion, go to Settings (CtrlAlt0S), navigate to Build, Execution, Deployment | Toolchain and select the toolchain that matches your Qt installation.

   If you have several Qt installations, make sure to select the same toolchain as the one you specified in CMAKE_PREFIX_PATH.

   As an example, in the case of MinGW:

   

tip

For more information about Windows toolchains, refer to the MinGW or MSVC section of our Windows Tutorial.

• Qt projects are handled as regular CMake projects in CLion, so you can configure CMake settings in Settings | Build, Execution, Deployment | CMake as necessary.

  For example, you can create different CMake profiles with different build types and set up CMake generators of your choice.

  In this dialog, you can also specify CMake options, such as CMAKE_PREFIX_PATH instead of setting them in CMakeLists.txt:

  

You can use Qt type renderers, which are usually shipped with Qt tools, for your project in CLion. However, for now, you need to set them manually either using the .gdbinit/.lldbinit scripts or, in the case of MSVC, via native visualizers.

• Windows MSVC

  CLion’s debugger for the MSVC toolchain can employ native visualizers if you have them in your project. Make sure to set the Enable NatVis renderers for LLDB option in Settings | Build, Execution, Deployment | Debugger | Data Views | C/C++.

  For example, copy qt5.natvis under your project root, and CLion will automatically detect and use it for rendering.

• Windows MinGW / macOS / Linux

  For non-MSVC toolchains, a solution would be to configure the Qt renderers via .gdbinit/.lldbinit. These scripts are loaded on every invocation of GDB or LLDB, respectively.

  1. You can try KDevelop formatters for GDB, KDevelop formatters for LLDB, Lekensteyn's qt5printers (GDB), or create your own pretty-printers.

     To create custom pretty printers, follow the official instructions for LLDB or GDB. You can take the pretty-printers for Rust implemented in the IntelliJ Rust plugin as a reference.

  2. Point the debugger to your renderers via .gdbinit/.lldbinit. Find an example in this github repo.

  3. Place the .gdbinit/.lldbinit files under the project root and allow them in your home directory as described here.

By default, CLion opens .ui files in Qt Designer.

The IDE searches for the path to Qt Designer in the Qt binaries folder specified in Settings | Languages & Frameworks | QML.

If you installed Qt Designer separately from Qt, CLion might not detect it and will open the .ui files in the editor. In this case, do the following to open them in Qt Designer:

1. Go to Settings | Editor | File Types.

2. Select Qt UI Designer Form from the Recognized File Types list, and delete the associated file extension:

   

3. Select Files opened in associated applications and add the .ui extension:

   

4. Cick Reassign Wildcard.

5. Click Apply and close the dialog.

   Next time you double-click a .ui file in the Project tree, it will be opened in Qt Designer.

1. In the Project view, select New from the context menu or press AltInsert. Choose Qt UI Class:

   

2. In the dialog that opens, fill in the class name and configure the following settings:

   • Filename base - specify the name for the .ui/.cpp/.h files to be generated.

   • Parent class - select QWidget, QMainWindow, QDialog, or a custom parent class.

   • Namespace - specify the enclosing namespace if required.

   • Add to targets - set this checkbox to automatically add the new files to the list of sources for the selected target(s).

   

3. CLion will generate the .ui, .cpp, and .h files following the templates defined in Settings | Editor | File and Code Templates: Qt Designer Form, Qt Class, and Qt Class Header, respectively. If required, you can adjust these templates for your needs.

   

1. Add the path to bin under the MinGW directory in the Qt installation (for example, C:\Qt\5.15.1\mingw81_64\bin) to the system PATH or in the Environment variables field of the configuration settings.

   If this doesn't solve the issue for your project, try Option 2.

1. Copy the .dll-s located in bin under the MinGW directory in the Qt installation to your project’s generation folder, which is cmake-build-debug or cmake-build-release by default.

   The libraries you will most likely need are libstdc++-6.dll, Qt5Widgets.dll, Qt5Gui.dll, and Qt5Core.dll, but your setup might require other libraries as well.

2. In the settings of the configuration you use for running, set the QT_QPA_PLATFORM_PLUGIN_PATH environment variable to plugins\platforms under the MinGW directory:

   

   tip

   Another option is to copy the contents of plugins\platforms to cmake-build-debug(release)/platforms (make sure to create the platforms directory).

   For more information, refer to Qt Plugins.