<div class="gmail_quote">On Thu, Oct 8, 2009 at 7:44 AM, Jeroen Dierckx <span dir="ltr"><<a href="mailto:jeroen.dierckx@gmail.com">jeroen.dierckx@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<div><br></div><div>One of our static libraries is a thin C++ wrapper on top of expat. I want to hide dealing with expat from the users of this library, which is no problem as I can link in the static expat library with my lib. The user can just include and link with my XmlParser library.</div>
<div><br></div><div>I linked the expat library with my static library in my cmake file (target_link_libraries), but this isn't reflected in my Visual Studio 2008 project (Librarian/General/"Additional Dependencies" and "Additional Library Directories"). This has the result that the users of my XmlParser library have to link with expat themselves.</div>
<div><br></div><div>Is this a deliberate feature of cmake? I know that when using cmake as a build system, expat is automatically linked when linking with my XmlParser library, but in my opinion there should at least be an option to actually link the dependencies in. Note that everything does work as expected when building a SHARED library in stead of a STATIC one.</div>
</blockquote><div><br>You might be able to use this:<br><a href="http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:STATIC_LIBRARY_FLAGS">http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:STATIC_LIBRARY_FLAGS</a><br>
<br></div></div>-- <br>Philip Lowman<br>