On 2016-10-10 21:30 +0000, Holger Levsen wrote: > Hi Helmut, > > On Mon, Oct 10, 2016 at 08:39:39PM +0200, Helmut Grohne wrote: > > dpkg-cross is deprecated by its former maintainer and ought to be > > removed. > > this seems a fairly strong statement, considering > https://tracker.debian.org/pkg/dpkg-cross shows not a single bug filed > against the package.
Now that dpkg-cross has had its RC bug fixed, I am happy to keep it in maintenance mode. It is not useless. It is also the source package from which cross-config comes, and that remains important. So no it's shouldn't be RMed. And yes I'm looking after it. I have just done the formal adoption upload to make this clearer As to the more interesting question of how best to deal with cmake cross-building, I wish I knew what the correct thing to do is. It is clearly better to have dpkg and debhelper conspire to set things up so that they 'just work' if we can. Because we have multiarch there is a good chance that this can be done in such a way that both native and cross building work with the same config. But I must admit that I have never managed to fully grok what was done in cmake to make multiarch crossbuilding work. I did recently mess with a cmake package and I specified -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) in an override_dh_auto_configure: to get it to build with multiarch paths. but this was not sufficient for the library to get put in $(DEB_HOST_MULTIARCH) even inthe native build. Indeed I was wondering where the right place to ask about this sort of thing is? the CmakeLists.txt file just says set(libdir ${CMAKE_INSTALL_LIBDIR}) and after that the pkgconfig file ends up in the right (multiarch) place, but the library itself doesn't. Anyone know what might be up there? (The offending package there is ne10, which is not yet uploaded, because the multiarch path is only partially working) /end digression. cross-config exists as a place for extra cross configuration that is not (yet) catered for by our other systems. As we move things into dpkg and debhelper it will ideally become obsolete, but I don't think we are there yet. It is true that Helmut has spend a lot more time on this recently than I have. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: Digital signature