On 22 December 2015 at 17:05, Michael Terry <michael.te...@canonical.com> wrote: > So I am also unsure of what exactly your scenario is (what the > reproduction steps are). > > Without any environment variables, cross compiling isn't used, so this > bug isn't hit. It's only when you set environment variables to use > cross compilers that you might hit this scenario. But if you look at, > for example, dpkg-cross(1), it recommends setting: > > export CC=$(DEB_HOST_GNU_TYPE)-gcc > export CXX=$(DEB_HOST_GNU_TYPE)-g++ > export CMAKE_TOOLCHAIN_FILE=/etc/dpkg-cross/cmake/CMakeCross.txt > > Thus manually setting CMAKE_TOOLCHAIN_FILE seems to be a standard part > of the documentation. What steps are you using to cross compile?
that's for debian. i've patched ubuntu cmake toolchain files to be sensitive to DEB_HOST|BUILD_ARCH and thus not requiring any special variables to be exported. This enabled cross-compilation of most cmake projects and debian packages out of the box on ubuntu, e.g. in chroots such as prepared with mk-sbuild and/or click chroot without any modifications to build rules. As per debian policy, one should be able to build projects twice in a row, if and only if a full clean is done in between. e.g. ./debian/rules build clean build -> should work, and it does work with these patches. I'm not sure what bug is hit and why. Because one should purge all of build dir to get cmake caches to its senses =0 -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472314 Title: Fix subsequent cmake runs when using multi-arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1472314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
