> It explains, why the library names are cutted, Why? Everything that can be found automatically by the compiler is transformed from
/path/to/libmylib.a to (-Wl,-Bstatic) -lmylib (-Wl,-Bdynamic) ? That's what I would like to avoid (the -Wl add-ons anyway). About "choosing" static vs. dynamic, I found http://www.cmake.org/cmake/help/cmake2.6docs.html#prop_tgt:LINK_SEARCH_END_STATIC -- no idea if this is still up-to-date. It doesn't help me much anyways since this is a fixed property of the target. --Nico On Fri, Jun 21, 2013 at 8:47 PM, Andreas Naumann <[email protected]>wrote: > It explains, why the library names are cutted, but it does not explain, > why cmake sometimes chooses static and sometimes dynamic libaries. It > should consequently set static for each library in the given list. > > Andreas > > > On 21.06.2013 20:34, Nico Schlömer wrote: > >> That's true indeed: The compiler is able to find netcdf by itself. >> Something like >> >> $ cc test.o -lnetcdf >> >> doesn't fail on the machine that I'm working on. I don't understand why >> it would do the translation there though. >> >> --Nico >> >> > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/** > opensource/opensource.html<http://www.kitware.com/opensource/opensource.html> > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/**CMake_FAQ<http://www.cmake.org/Wiki/CMake_FAQ> > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/**listinfo/cmake<http://www.cmake.org/mailman/listinfo/cmake> >
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
