|
|
| (4 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| Qt Creator is an IDE from Qt.
| | Moved to https://develop.kde.org/docs/getting-started/building/ide/qt-creator/ |
| | |
| A screen recording version is available https://www.youtube.com/watch?v=ASnDeEaXnbI
| |
| | |
| == Features ==
| |
| | |
| Qt Creator is a good choice when starting to contribute to KDE.
| |
| | |
| Qt Creator has: support for kdesrc-build, a good debugger, source code navigation, Qt widgets UI designer, basic QML editor, QML debugger, Qt resources editor, Qt project templates, good CMake support, C++ static analyzers.
| |
| | |
| Additional features:
| |
| * Source code navigation: switch header/source, follow symbol, switch between function declaration/definition, find references, open type hierarchy, open include hierarchy.
| |
| * Refactor rename symbol.
| |
| * Views: class view, tests view, document outline view and document outline combo box, CMake structure view, file system view.
| |
| | |
| For best results, download Qt Creator from the Qt website. https://www.youtube.com/watch?v=QVgInye6HDA
| |
| | |
| ==kdesrc-build==
| |
| | |
| After you configure kdesrc-build and you can correctly build a KDE project such as kcalc.
| |
| | |
| Edit ~/.config/kdesrc-buildrc . It should look like:
| |
| | |
| <syntaxhighlight lang="ini">
| |
| ...
| |
| include-dependencies true
| |
| ...
| |
| kdedir ~/kde/usr
| |
| ... | |
| source-dir ~/kde/src
| |
| ...
| |
| build-dir ~/kde/build
| |
| ...
| |
| cmake-options -DCMAKE_BUILD_TYPE=Debug
| |
| ...
| |
| </syntaxhighlight>
| |
| | |
| The line above is important in order to use the debugger from Qt Creator.
| |
| | |
| Make sure you have the correct number on the line <code>num-cores </code>.
| |
| | |
| Build kcalc, make sure there are no errors:
| |
| {{Input|1=<nowiki>
| |
| kdesrc-build kcalc
| |
| </nowiki>}}
| |
| | |
| ==Install Qt Creator==
| |
| | |
| Install Qt Creator. E.g. download from the Qt website https://www.qt.io/ the latest version. Video version https://www.youtube.com/watch?v=QVgInye6HDA
| |
| | |
| The newest version of Qt Creator installed from the Qt website will have the latest features and the latest bug fixes.
| |
| | |
| Or e.g. from your current Linux distribution's packages. E.g.
| |
| {{Input|1=<nowiki>
| |
| apt install qtcreator
| |
| </nowiki>}}
| |
| | |
| ===QML Designer===
| |
| | |
| Qt Creator has a "forms editor" for QML. You can enable it from the Qt Creator main menu > Help > About Plugins... > Qt Quick > enable "QmlDesigner". If it asks you to restart Qt Creator, do it.
| |
| | |
| Test it. From Qt Designer main menu > File > Close all Files and Editors. File > New Project... > Application (Qt) > Qt Quick Application, finish the wizard correctly. Open the file "Main.qml" in "Switch to Edit mode Ctrl+2". In the left hand side, choose "Switch to Design mode Ctrl+3".
| |
| | |
| From the Qt Creator main menu > View > Workspaces > Views-All. Close all of the tool windows (views) that you do not need, e.g. "3D", "States", "Timeline", "Curves", "Transitions".
| |
| | |
| ==Load a KDE git repository in Qt Creator==
| |
| | |
| We use kcalc as the example KDE git repository. Make sure it was built correctly using kdesrc-build.
| |
| | |
| <pre>
| |
| kdesrc-build kcalc
| |
| </pre>
| |
| | |
| Start Qt Creator. E.g. from the KDE Application Launcher (or from KRunner Alt+F2).
| |
| | |
| From the qtcreator main menu
| |
| | |
| File > Close All Projects and Editors
| |
| | |
| File > Open File or Project <code>~/kde/src/kcalc/CMakeLists.txt</code>
| |
| | |
| Left Sidebar > Switch to Projects mode Ctrl+5 > Manage Kits...
| |
| | |
| [[File:Qt creator manage kits.png|border|300px|Manage Kits]]
| |
| | |
| Under "Kits > Manual", remove all kits except "Desktop (default)" or "Qt (default)". E.g. select Manual > "Imported Kit" > press the "Remove" button > press the "OK" button. Make sure that you have removed all kits with name ending in "- temporary".
| |
| | |
| [[File:Qt creator remove all kits except desktop.png|border|500px|Remove all kits, except Desktop]]
| |
| | |
| Button "Import Existing Build..." > Directory: ~/kde/build/kcalc > Choose.
| |
| | |
| [[File:Qt creator import existing build.png|border|300px|Import Existing Build]]
| |
| | |
| CMake should be configured correctly. CMake is run automatically, see "General Messages Alt+7".
| |
| | |
| Left Sidebar > Switch to Projects mode Ctrl+5 > Active project: kcalc. Build & Run: not the Desktop kit (e.g. "Imported Kit") > Build.
| |
| | |
| [[File:Qt creator kit build configuration.png|border|250px|kit build configuration]]
| |
| | |
| Build Settings > Edit build configuration: "Debug2".
| |
| | |
| [[File:Qt creator build settings debug2.png|border|500px|build settings debug2]]
| |
| | |
| Translate the content of the file <code>~/kde/build/kcalc/prefix.sh</code> to the syntax of Qt Creator "Batch Edit". E.g. for Debian based distributions if <code>~/kde/build/kcalc/prefix.sh</code> is like:
| |
| | |
| <syntaxhighlight lang="bash">
| |
| export PATH=/home/username/kde/usr/bin:$PATH
| |
| | |
| # LD_LIBRARY_PATH only needed if you are building without rpath
| |
| # export LD_LIBRARY_PATH=/home/username/kde/usr/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH
| |
| | |
| export XDG_DATA_DIRS=/home/username/kde/usr/share:${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}
| |
| export XDG_CONFIG_DIRS=/home/username/kde/usr/etc/xdg:${XDG_CONFIG_DIRS:-/etc/xdg}
| |
| | |
| export QT_PLUGIN_PATH=/home/username/kde/usr/lib/x86_64-linux-gnu/plugins:$QT_PLUGIN_PATH
| |
| export QML2_IMPORT_PATH=/home/username/kde/usr/lib/x86_64-linux-gnu/qml:$QML2_IMPORT_PATH
| |
| | |
| export QT_QUICK_CONTROLS_STYLE_PATH=/home/username/kde/usr/lib/x86_64-linux-gnu/qml/QtQuick/Controls.2/:$QT_QUICK_CONTROLS_STYLE_PATH
| |
| </syntaxhighlight>
| |
| | |
| Then the same thing in the syntax of Qt Creator "Batch Edit" looks like this block of text:
| |
| | |
| <syntaxhighlight lang="bash">
| |
| PATH=+/home/username/kde/usr/bin
| |
| XDG_DATA_DIRS=+/home/username/kde/usr/share
| |
| XDG_CONFIG_DIRS=+/home/username/kde/usr/etc/xdg
| |
| QT_PLUGIN_PATH=+/home/username/kde/usr/lib/x86_64-linux-gnu/plugins
| |
| QML2_IMPORT_PATH=+/home/username/kde/usr/lib/x86_64-linux-gnu/qml
| |
| QT_QUICK_CONTROLS_STYLE_PATH=+/home/username/kde/usr/lib/x86_64-linux-gnu/qml/QtQuick/Controls.2/
| |
| </syntaxhighlight>
| |
| | |
| Note: if you want to see debugging messages, you can add corresponding variables here. See [[Guidelines and HOWTOs/Debugging/Using Error Messages#Controlling_Messages]]
| |
| | |
| You probably want to save the above block of text, in order to reuse it when loading other KDE git repositories in Qt Creator. E.g. to file <code>~/kde/qtcreator_run_environment.txt</code>.
| |
| | |
| Left Sidebar > Switch to Projects mode Ctrl+5 > Build & Run: not the Desktop kit (e.g. "Imported Kit") > Run. Run Settings > Run > Run configuration: select "kcalc". This is the CMake executable target for the GUI application kcalc. The other items in the combobox e.g. "knumbertest" are binary executable (CTest type) tests.
| |
| | |
| [[File:Qt creator run target.png|border|500px|run target]]
| |
| | |
| Environment > Use Build Environment > press the Details button > press the "Reset" button if possible > press the "Batch Edit..." button. Paste in there, the text block that you prepared above, then press the OK button.
| |
| | |
| [[File:Qt creator run environment.png|border|700px|run environment]]
| |
| | |
| Click on the left sidebar, the button above "Run Ctrl+R". It should show: Project: kcalc. Kit: not the Desktop kit (e.g. "imported Kit"). Deploy: Deploy Configuration. Build: Debug2. Run: kcalc.
| |
| | |
| [[File:Qt creator project button above run.png|border|200px|project button above run]]
| |
| | |
| CMake configure was run automatically. You can run it again from the Qt Creator main menu > Build > Run CMake.
| |
| | |
| You can build by pressing the hammer icon on the lower left with tooltip "Build Project Ctrl+B". Or from the Qt Creator main menu > Build > "Build Project Ctrl+B".
| |
| | |
| Left Sidebar > Switch to Edit mode (Ctrl+2) > Select "Projects" from the combobox (the other interesting combobox item is "File System"). In the "Projects" left hand treeview > kcalc > kcalc > Source Files > double click on the file kcalc.cpp. The file kcalc.cpp will be shown in the editor view. Click inside the source code in text editor.
| |
| | |
| [[File:Qt creator open file in editor.png|border|300px|open file in editor]]
| |
| | |
| In the text editor's top bar > function/identifier/method/type/symbols combobox, select the last item: <code>main(int, char**) -> int</code>. Click on the line with the opening curly bracket of the function main. From the main menu > Debug > Set or Remove Breakpoint (F9).
| |
| | |
| Left Sidebar > Start debugging of startup project. The debugger will start correctly and break on the source code line with the curly bracket.
| |
| | |
| From the main menu Debug > Step Over (F10)/Step Into(F11)/Step Out (Shift+F11).
| |
| | |
| ==Enable parallel jobs in Qt Creator==
| |
| | |
| * Left Sidebar > Switch to Projects mode (Ctrl+5).
| |
| * Under the Build settings of the imported kit find the "Build Steps" option.
| |
| * Click on the "Details" button on the right side of the "Build Steps" option to access the detailed build configuration.
| |
| * Under the "Tool arguments" field add the argument <code>-j<jobs></code>. Replace "<jobs>" with the desired number of parallel jobs you want to use during compilation. For example, if you have a CPU with 16 threads and want to use 12 parallel jobs, you would enter <code>-j12</code>.
| |
| [[File:Qt creator parallel jobs.png|border|600px|Parallel jobs]]
| |
| * Rebuild your project to get faster compilation.
| |
| | |
| == Tips and Tricks ==
| |
| | |
| === Custom executable to run ===
| |
| | |
| When developing a library, it may be convenient to launch some application that uses it, from the current project. For example, you work with Ark's libraries used in dolphin context menu actions. You can make your run configuration to launch custom binary - dolphin. See [https://doc.qt.io/qtcreator/creator-run-settings.html#specifying-a-custom-executable-to-run documentation] on how to configure that.
| |
