Cross qmake to the chroots

[Zoltan Balogh]

The https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.3.2+dfsg-4ubuntu3 release of the QtBase module provides the new qt5-qmake-cross-armhf package and so the /usr/bin/qt5-qmake-cross-armhf binary.

This qmake binary is made for x86 chroots with armhf development target.

This change is to enable the build of qmake project type in the click chroot.

In order to support qmake projects we need this package installed in the click chroot. The qt5-qmake-cross-armhf is not a multiarch package, it is made exclusively for i386 and amd64 targets.

[Alberto Mardegan (mardy)]

Any expected release date for this?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Zoltan Balogh (bzoltan)]

While mvo is working on the next click release the workaround is available in the SDK PPA -> https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/ppa?field.series_filter=vivid

[Alberto Mardegan (mardy)]

Ah, thanks! I'll get it from there, then!

[Alberto Mardegan (mardy)]

This doesn't work from the SDK PPA either. When I try to build a project in QtCreator I get:

=====
00:39:50: Running steps for project imaginario...
00:39:50: Starting: "/home/mardy/.config/ubuntu-sdk/ubuntu-sdk-14.10-armhf/qt5-qmake-arm-linux-gnueabihf" /media/mardy/Data/src/git/imaginario/imaginario.pro -r -spec linux-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug
00:39:50: The process "/home/mardy/.config/ubuntu-sdk/ubuntu-sdk-14.10-armhf/qt5-qmake-arm-linux-gnueabihf" exited with code 1.
Error while building/deploying project imaginario (kit: UbuntuSDK for armhf (GCC ubuntu-sdk-14.10-utopic))
When executing step 'qmake'
00:39:50: Elapsed time: 00:00.
=====

The if I go to Tools->Options->Ubuntu->Maintain (on the armhf target), and I type qmake from the chroot terminal, I get:

=====
(click-ubuntu-sdk-14.10-armhf)root@mardy-VirtualBox:/home/mardy# qmake
qmake: could not find a Qt installation of ''
=====

[Nathan Osman (george-edison55)]

This bug also affects packages cross-compiled for armhf that attempt to use qmake:

$ sbuild --build=amd64 --host=armhf -d trusty myapp_1.0.dsc

...

   dh_auto_configure -a
qmake: could not find a Qt installation of ''
dh_auto_configure: qmake -makefile -nocache QMAKE_CFLAGS_RELEASE=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CFLAGS_DEBUG=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CXXFLAGS_RELEASE=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CXXFLAGS_DEBUG=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_LFLAGS_RELEASE=-Wl,-Bsymbolic-functions -Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-Bsymbolic-functions -Wl,-z,relro QMAKE_STRIP=: PREFIX=/usr returned exit code 1
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

[Zoltan Balogh (bzoltan)]

Just to clarify a simple detail: the qmake support is available only from the 15.04 chroots