---
category: en
type: paper
layout: paper
tags: archlinux, linux, building, qutim
title: Building Qutim using Qt5
short: building-qutim-using-qt5
description: Qutim is a multiprotocol and cross platform messenger. It is written on CPP
using Qt library. The project is actively developed. In this paper I will say about building this package in Archlinux using Qt5 library (instead of Qt4 which is used in current AUR packages).
---
This package uses qbs for building, which is a bit strange IMHO. A package, which is necessary for building, is in AUR . I recommend to use git version of the package. When I asked Andrea Scarpino (who maintains KDE and Qt packages into the official repos) about qbs, he told me "we will support it in time". And I agree with him, the project seems to be a little unstable.
Install dependences. I had used namcap
, so maybe I missed something:
You may read about qbs on the link or see examples which are provides by the package. qbs uses configuration file that firstly you must create and secondly it is stored in your home directory. In theory a configuration file creating ((~/.config/QtProject/qbs.conf
)) looks like this:
Firstly we find Qt libraries. Then we find toolchains (such as compilers). And next we must insert a toolchain into Qt profile (for example, we need clang
toolchain):
And there are other ways. You may edit the file manually or use qbs-config-ui
or qbs-config
.
So, we have created the configuration file and put it into build directory:
{% highlight ini %} [General] [Qt] filedialog= [profiles] clang\cpp\compilerName=clang++ clang\cpp\toolchainInstallPath=/usr/bin clang\qbs\architecture=x86_64 clang\qbs\endianness=little clang\qbs\toolchain=clang, llvm, gcc gcc\cpp\compilerName=g++ gcc\cpp\toolchainInstallPath=/usr/bin gcc\qbs\architecture=x86_64 gcc\qbs\endianness=little gcc\qbs\toolchain=gcc qutim\Qt\core\binPath=/usr/lib/qt/bin qutim\Qt\core\buildVariant=release qutim\Qt\core\config=shared, qpa, no_mocdepend, release, qt_no_framework qutim\Qt\core\docPath=/usr/share/doc/qt qutim\Qt\core\incPath=/usr/include/qt qutim\Qt\core\libInfix= qutim\Qt\core\libPath=/usr/lib qutim\Qt\core\mkspecPath=/usr/lib/qt/mkspecs/linux-g++ qutim\Qt\core\namespace= qutim\Qt\core\pluginPath=/usr/lib/qt/plugins qutim\Qt\core\qtConfig=minimal-config, small-config, medium-config, large-config, full-config, gtk2, gtkstyle, fontconfig, libudev, evdev, xlib, xcb-glx, xcb-xlib, xcb-sm, xrender, accessibility-atspi-bridge, linuxfb, c++11, accessibility, opengl, shared, qpa, reduce_exports, reduce_relocations, clock-gettime, clock-monotonic, mremap, getaddrinfo, ipv6ifname, getifaddrs, inotify, eventfd, system-jpeg, system-png, png, system-freetype, no-harfbuzz, system-zlib, nis, cups, iconv, glib, dbus, dbus-linked, openssl-linked, xcb, xinput2, alsa, pulseaudio, icu, concurrent, audio-backend, release qutim\Qt\core\version=5.2.0 qutim\cpp\compilerName=clang++ qutim\cpp\toolchainInstallPath=/usr/bin qutim\qbs\architecture=x86_64 qutim\qbs\endianness=little qutim\qbs\toolchain=clang, llvm, gcc {% endhighlight %}The first problem is clang
(at least in Archlinux):
The second one is qbs:
{% highlight diff %} diff -ruN qutim.orig/protocols/jabber/jreen/jreen.qbs qutim/protocols/jabber/jreen/jreen.qbs --- qutim.orig/protocols/jabber/jreen/jreen.qbs 2014-01-06 15:41:33.000000000 +0400 +++ qutim/protocols/jabber/jreen/jreen.qbs 2014-01-06 15:44:54.502175067 +0400 @@ -2,7 +2,7 @@ Project { - moduleSearchPaths: "qbs/modules" + qbsSearchPaths: "qbs/modules" references: "src/src.qbs" } {% endhighlight %}And the last one is Vk plugin:
{% highlight diff %} diff -ruN qutim.orig/protocols/vkontakte/vreen/vreen.qbs qutim/protocols/vkontakte/vreen/vreen.qbs --- qutim.orig/protocols/vkontakte/vreen/vreen.qbs 2014-01-06 15:41:42.000000000 +0400 +++ qutim/protocols/vkontakte/vreen/vreen.qbs 2014-01-06 15:46:47.142178486 +0400 @@ -5,6 +5,7 @@ property string vreen_qml_path: "bin" property string vreen_lib_path: "lib" property string vreen_libexec_path: "lib" + property string lib_path: "lib" property string vreen_version_major: 1 property string vreen_version_minor: 9 {% endhighlight %}I want to create a universal recipe for the building, thus we must set $HOME
directory. Flag -j
means number of jobs, -d
means build directory, release
means building type (debug, release), profile
is used profile, which is described in the configuration file.
We must set root directory (--install-root
), because without this option the package will be installed into /
(/bin
and /lib
).