On Mon, Apr 24, 2017 at 19:58:52 +0100, Roger Leigh wrote: > While you can install as many of the runtime packages as you like, the > headers go into /usr/include and so they conflict with each other, > limiting you to a single development package at one time (checked the > behaviour to verify this, and installing one triggers removal of any > existing variant). Not itself a multiarch limitation--many packages now > use /usr/include/<arch> for this reason--but certainly a limitation in > the packaging of the current libpng, which for some reason hasn't yet > started using arch-specific headers.
Hmm, odd. Coming from RPM, it copes with multiple -devel packages all writing directly to `/usr/include` as long as the headers themselves are the same on all architectures (and, IIRC, binaries are decided based on the "preferred" architecture of the host in case of conflicts). Oddities in packaging formats I suppose :) . --Ben -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers