<div dir="auto">Hi Chris,<div dir="auto"><br></div><div dir="auto">Are you, by any chance, using (via find_package), another library that may have been built with tbb support? </div><div dir="auto">I've had the exact same problem you describe with OpenCV, when my own targets link against the opencv ones. </div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Luis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 13 Oct 2017 01:21, "Chris Green" <<a href="mailto:greenc@fnal.gov">greenc@fnal.gov</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  

    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <p>Hi,</p>
    <p>Using CMake 3.9.2, I'm trying to ascertain where an instance of
      '-ltbb' is getting injected into the link command line of some of
      our executables. This is bad because we can't find it anywhere in
      our source (we have a config CMake that uses the full path to the
      library), and the system TBB library is being picked up which is
      wrong (old version compiled with wrong compiler to wrong C++
      standard). I have verified that we have no explicit use of '-ltbb'
      anywhere, and also that LIBRARY_PATH is not being set in the
      environment. Two questions arise:</p>
    <ol>
      <li>How can I trace what is going into the link.txt files, and
        whence?</li>
      <li>Are there any remaining mechanisms for explicit conversion
        from X/Y/Z/libQ.so to -lQ that I'm unaware of?</li>
    </ol>
    <p>It should be noted as a matter of form that the link.txt contains
      a *whole* lot of stuff that wasn't explicitly put there by the
      target_link_libraries() command, and that turns out to be
      superfluous.</p>
    <p>Any help in this matter would be gratefully received, because too
      much of this is currently a black box to me and I'm lost.</p>
    <p>Thanks,</p>
    <p>Chris.<br>
    </p>
  </div>

<br>--<br>
<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" rel="noreferrer" target="_blank">http://www.cmake.org/Wiki/<wbr>CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake community. For more information on each offering, please visit:<br>
<br>
CMake Support: <a href="http://cmake.org/cmake/help/support.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/<wbr>support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/<wbr>consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" rel="noreferrer" target="_blank">http://cmake.org/cmake/help/<wbr>training.html</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/cmake" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/cmake</a><br></blockquote></div></div>