...except that the fix is only the upstream one, not the similar change to our own mkspec.
To reproduce:
bzr branch lp:telegram-app
vi telegram-app/scope/scope.pro # remove the PKG_CONFIG_LIBDIR line as instructed
sudo chroot /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-ucca-1000-* # your directory here
# navigate to telegram-app
qt5-qmake-arm-linux-gnueabihf .
Result:
Project ERROR: libunity-scopes development package not found
Expected:
No error.
However, even adding the same lines that were added in upstream to our own usr/lib/arm-linux-gnueabihf/qt5/mkspecs/ubuntu-arm-gnueabihf-g++/qmake.conf inside the chroot, the error message is still there.
...except that the fix is only the upstream one, not the similar change to our own mkspec.
To reproduce:
bzr branch lp:telegram-app app/scope/ scope.pro # remove the PKG_CONFIG_LIBDIR line as instructed
vi telegram-
sudo chroot /var/lib/ schroot/ mount/click- ubuntu- sdk-15. 04-armhf- ucca-1000- * # your directory here arm-linux- gnueabihf .
# navigate to telegram-app
qt5-qmake-
Result:
Project ERROR: libunity-scopes development package not found
Expected:
No error.
However, even adding the same lines that were added in upstream to our own usr/lib/ arm-linux- gnueabihf/ qt5/mkspecs/ ubuntu- arm-gnueabihf- g++/qmake. conf inside the chroot, the error message is still there.