This is still an issue, and very confusing. I assume that most developers who need external dependenices for the click package run into this and wonder why the linker complains about not finding the library.
I guess most developers find it more convenient to add build rules that copy prebuilt libraries from the chroot into the click package instead of adding the library source code to their project. This ensures easy click package updates whenever Ubuntu updates the library (without API breaking changes of course). For this use case, running apt-get install libwhatever-dev in the chroot is the first required step, and the user expects to have a somewhat sane environment when clicking the "Maintain" button. I worked around this by installing libupnp6:armhf and libupnp6-dev:armhf instead of libupnp-dev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322178 Title: new armhf click build chroot is DEB_BUILD_ARCH=amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1322178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
