Nils Gladitz <nilsglad...@gmail.com>
writes:
> On 06/25/2014 02:53 PM, Stephen Kelly wrote:
>> David Cole via cmake-developers wrote:
>
>> Thanks. That indeed doesn't seem to interact well with CMake.
>>
>> The introduction of imported targets is an opportunity to add the necessary
>> define to disable it to INTERFACE_COMPILE_DEFINITIONS by default, if that is
>> desired.
>
> I would like that very much as well.
I'll look into doing that. I think populating
INTERFACE_COMPILE_DEFINTIONS with BOOST_${LIBRARY_NAME}_NO_LIB seems the
obvious choice. In addition I can provide a Boost::disable_autolinking
target to disable it for the complete library.
> I've got a custom FindBoost.cmake which basically just wraps the
> actual FindBoost module and sets the "BOOST_ALL_NO_LIB" definition.
Another option is to wrap FindBoost and simply unset ${Boost_LIBRARIES}
on Windows after it completed and to make sure the link directories are
set.
> This seems to be a source of confusion for people who are unaware of
> autolinking in general.
>
> Having CMake find and link one set of libraries (DLL by default) and
> the lib pragmas link yet another set of libraries (static by default).
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
