Timo already nicely summed up our discussion :) I will leave my investigation here just for completeness: the fix applies to the "device" mkspec, which is the one (I guess) that is used when building using QtCreator with an ARM device target.
So it "should" fix that usecase (not tested). What it doesn't fix, is the usecase where you directly enter an arm chroot for crosscompilation purposes without using QtCreator. In that case the compilation goes through ubuntu-arm-gnueabihf-g++ makespec which is missing the correct PKGCONFIG path redirection that is done by https://codereview.qt-project.org/#/c/143276/2//ALL,unified -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1580981 Title: PKGCONFIG not working in SDK Status in Client Developer Experience: Confirmed Status in Ubuntu SDK IDE: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu RTM: Incomplete Bug description: having this in a qmake .pro file: CONFIG += link_pkgconfig PKGCONFIG += url-dispatcher-1 qmenumodel works fine for native building, but fails for crossbuilding for armhf. https://codereview.qt-project.org/#/c/143276/2//ALL,unified To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1580981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
