Calligra/Building/2/Developing With QtCreator: Difference between revisions
Appearance
fix KDEDIRS value |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
If everything is setup properly as explained here, you will be able to run Calligra apps and debug them from within Qt Creator. Git integration works too. | If everything is setup properly as explained here, you will be able to run Calligra apps and debug them from within Qt Creator. Git integration works too. | ||
{{Note|First, you have to get the source of Calligra and install all dependencies. That is described best in the [[ | {{Note|First, you have to get the source of Calligra and install all dependencies. That is described best in the [[Calligra/Building/2|Building Calligra 2.x]] article, which would be anyway a must read, if you are building the first time. Following recipes were tested for Calligra 2.x , QtCreator 2.x or newer and Qt 4.8.x. All paths here are kept similar to these explained on the ''Building Calligra'' page but make sure you use correct ones. }} | ||
{{Note|This is a simplified Calligra- and CMake- specific recipe, more extensive documentation is at [https://qt-project.org/doc/qtcreator-3.2/creator-project-cmake.html].}} | {{Note|This is a simplified Calligra- and CMake- specific recipe, more extensive documentation is at [https://qt-project.org/doc/qtcreator-3.2/creator-project-cmake.html].}} | ||
Latest revision as of 17:09, 9 May 2015
If everything is setup properly as explained here, you will be able to run Calligra apps and debug them from within Qt Creator. Git integration works too.
- Start Qt Creator, use File -> Open File or Project from the menu and select CMakeLists.txt file which is in the root of your Calligra source tree directory. The CMake wizard should start.
- In the Build Location wizard's page you can set a custom build directory. Better do not use the proposed one (/path/to/source/qtcreator-build) but /home/YOURLOGIN/kde4/build/calligra or something like this. If you built this code from command line before, it's best idea to use the same build dir as before. Thus you can use Creator-based and command line-based builds exchangeably.
- Click Next. On the Run CMake wizard page you should add at least the install-dir build option:
-DCMAKE_INSTALL_PREFIX=/home/YOURLOGIN/kde4/inst
Depending on what kind of build you want, you can also append these options:- For a build where you want to be able to obtain backtraces (good for bugfixing or reporting bugs)
-DCMAKE_BUILD_TYPE=DebugFull
- For building tests as well append
-DKDE4_BUILD_TESTS=ON
- For a fast running release build (not really useful for development).
-DKDE4_BUILD_TESTS=0 -DBUILD_TESTS=0 -DCMAKE_BUILD_TYPE=Release
- For a build where you want to be able to obtain backtraces (good for bugfixing or reporting bugs)
- After finishing the wizard, change to the Project view.
- Edit the Make build step and set the Additional arguments to:
-j5 install
(change 5 to other number as explained at [2]) - Add the variables to the build environment as listed below. You can use the Batch Edit button for convenience. See also Qt Creator Manual. Note you cannot use $HOME and other variables there. Compare to [3]. Replace paths containing lib64 with other if your OS is 32 bit.
CMAKE_PREFIX_PATH=/home/YOURLOGIN/kde4/inst
KDEDIRS=/home/YOURLOGIN/kde4/inst
KDEHOME=/home/YOURLOGIN/kde4/inst/.kde4
KDESYCOCA=/var/tmp/kdedev-YOURLOGIN/ksycoca
KDETMP=/tmp/kdedev-YOURLOGIN
KDEVARTMP=/var/tmp/kdedev-YOURLOGIN
KDE_INSTALL_PREFIX=/home/YOURLOGIN/kde4/inst
LD_LIBRARY_PATH=/home/YOURLOGIN/kde4/inst/lib64
PATH=/home/YOURLOGIN/kde4/inst/bin:/usr/bin:/usr/local/bin:/bin:/usr/bin/X11:/usr/X11R6/bin
PKG_CONFIG_PATH=/home/YOURLOGIN/kde4/inst/lib64/pkgconfig
QT_PLUGIN_PATH=/home/YOURLOGIN/kde4/inst/lib64/kde4/plugins
- Assure, that in Run Settings Run Environment is set to Use Build Environment
- Now in project's Run Settings you can select in the Run configuration which program should start when you execute Run or Debug.