title: cmake and deb dependencies
body: <p>Suppose I have a CMake project with <code>exectuable A</code> and shared <code>library B</code>. Library B is also dependent of the <code>crypto</code> library, and links to it dynamically. <code>Library B</code> is also <em>publicly</em> dependent of <code>crypto</code> (maybe it uses a function from there in a header file). This is easy to express in CMake as a transitive (public) dependency, so that <code>crypto</code> dependency does not need to be specified for <code>executable A</code>.</p>
  <p>However, I would also like to to have the possibility to alternatively have <code>library B</code> built as a Debian dev package, install it in a known location and link to it from CMake when building <code>executable A</code>. The CMake info about the transitative dependency is thereby lost (that is, that I also have to link to <code>libcrypto</code>). What is the correct way to solve this?</p>