Hi all.<br><br>I have a question regarding library dependency.<br>Im using VC2005.<br><br><br>Assume the following:<br><br>I have a solution with a set of projects, three are libraries and one is an application:<br><br>A.lib
/A.dll <br><br>B.lib/B.dll
: B depends on A.lib, so if I want to use B.lib somewhere, A.lib is
also automatically added as a link dependency. Also B.lib depends on
X.lib which is a library external to the solution.<br>X.lib
is also a X.lib/X.dll<br><br><br>C.lib, depends on B.lib, so in the list of libraries in Additional Libraries, is now: A.lib, B.lib, X.lib <br><br><br>Application APP depends on C, so the list of libraries is then: A.lib
, B.lib, X.lib, C.lib<br><br><br>Now
if X.lib is a library with the implementation in a dynamic library, one
does not need to link C nor APP against X.lib because it is implicitly
already linked against B.lib<br><br><br>My question is now, is there a way to tell CMake to not include
X.lib (which is needed to build B.lib only) when using B.lib?<br>Otherwise the list of libraries in Additional LIbraries tends to be pretty long...<br><br>It seems that Cmake always assumes that all libraries including their dependencies should be used when building.
<br>I realize that there is perhaps no way for CMake to automatically realize whether a library should be included or not...<br>But is there a way around this?<br><br clear="all"><br>-- <br><br><br>________________________________________________________________
<br> Anders Backman Email: <a href="mailto:andersb@cs.umu.se">andersb@cs.umu.se</a><br> HPC2N/VRlab Phone: +46 (0)90-786 9936<br> Umea university Cellular: +46 (0)70-392 64 67
<br> S-901 87 UMEA SWEDEN Fax: +46 90-786 6126<br> <a href="http://www.cs.umu.se/~andersb">http://www.cs.umu.se/~andersb</a>