> No, the 'linker' does not complain. You're right, it is the CMake dependency checker. The linking is all right, but there's something amiss with the CMake export files. I'll investigate.
Thanks for the comments! --Nico On Thu, Mar 20, 2014 at 3:31 PM, Mathieu Malaterre <mathieu.malate...@gmail.com> wrote: > Hi > > On 3/20/14, Nico Schlömer <nico.schloe...@gmail.com> wrote: >> I'm building a package for a library A that depends on another >> library, libB.so (from its dev-version). When installing library A, >> the package libb is installed, containing libB.so.7.2 and libB.so.7. >> When linking an executable against libA.so, the linker rightfully >> complains about a missing libB.so. > > No, the 'linker' does not complain. > >> What is the correct fix here? > > You should check your build system. It seems to be broken. libB is an > implementation details of libA. Application programmer linking to libA > should *not* know about those low level technical details. Unless of > course explicitely stated in the documentation and/or provided in the > *.pc file (or cmake exported file). So unless you know what you are > doing libB should not appear on the link line. > > In any case if you have an application using libA API, but complains > about missing libB symbols, you have a case where libA is underlinked > which is a serious issue and should not happen in debian package. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAK6Z60etkwiZ-x-Z3dzhzORx04XV4fHscDt=fhdn9nfvrqe...@mail.gmail.com
