bcm
bcm copied to clipboard
Boost cmake modules
I'd like to incorporate bcm into our build system. Since there is no license file present in the repository I was wondering if you could add one. Thank you :)
This can help with integrated builds to disable installation of dependencies. When set to off, `bcm_install_targets` will be a no-op. This can probably even be a target-level property.
These properties are only named with `INTERFACE_` so they are whitelisted for interface libraries. Instead there should be a corresponding `bcm_target_` function to set the property.
Something like: ``` set_target_properties(${EXPORT_TARGETS} PROPERTIES DEBUG_POSTFIX "-d" SO_VERSION ${EXPORT_VERSION} VERSION ${EXPORT_VERSION} ) install(TARGETS ${EXPORT_TARGETS} EXPORT ${EXPORT_SET} ARCHIVE DESTINATION "${CMAKE_INSTALL_LIBDIR}" COMPONENT ${EXPORT_COMPONENT}_DEV LIBRARY NAMELINK_ONLY DESTINATION "${CMAKE_INSTALL_LIBDIR}" COMPONENT ${EXPORT_COMPONENT}_DEV LIBRARY CONFIGURATIONS Debug...
Since you have support in for COMPILE_ONLY in the bcm_test for paralleling the compile/compile-fail rules of Boost Build you can also add support for Boost Build link/link-fail rules with a...
See this comment from @eldiener: > Why not have the line: > > add_library(${PARSE_NAME} STATIC EXCLUDE_FROM_ALL ${SOURCES}) > > be instead: > > add_library(${PARSE_NAME} OBJECT EXCLUDE_FROM_ALL ${SOURCES}) > > if...
This is needed by boost.spirit examples.
Overall, I have two big concerns about this approach: * It is too tied to how Boost builds things and/or has incompatible Boost-specific workarounds. * BCM provides an alternative to...
For example, I want to be able to check that a specific error message is emitted (a `static_assert`, say). The way I do that right now is by putting the...
Or is it deprecated?