Please note the scope of this bug is very limited: * when running on a debian like system * which has multiarch enabled * and compiling under the environment as exported by dpkg-buildpackage (or similar, e.g. debuild, or launchpad PPA builders) * with cmake from trusty (highly experimental and volatile) * with a non-multiarch qt
Attaching a log which shows successful build in question when invoked in Debian policy compliant way: ./debian/rules build; fakeroot ./debian/rules binary, instead of invoking with a wrapper. In no way this is an upstream bug, but this is a purely packaging bug. The recent distro changes to cmake are intended to not cause any packaging changes, thus this is a regression. I think there are easy ways to fix this. Any claims that this is representative of ABI/API in Trusty, are widely exaggerated. Given that at this point in time Trusty is still early in development and is undergoing highly disruptive changes (e.g. major upstream release of eglibc, new libtool, new toolchain, new gtk, new boost, shortly new qt) this is bug is no more, than a regression in a weekly automated snapshot builds. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to cmake in Ubuntu. https://bugs.launchpad.net/bugs/1262273 Title: qt5 automoc detection is not smart enough, when system CMake is used with non-system qt5 (undeclared, toolchain-less sys-root/prefix builds) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1262273/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
