On Jun 17, 2017, at 6:08 AM, Peter Dimov via Boost
wrote: P F wrote:
bcm_setup_version(VERSION ${BOOST_VERSION})
When I see this my first thought is always "where do the bcm_ macros come from”?
Ideally, we should strive for libraries to work standalone.
Sorry, I skipped over that part. The bcm_ macros are another boost library that would be installed and found with `find_package`. I was just trying to transform the code I linked to, but ideally, it would written like this: find_package(BCM) find_package(boost_config) # Use main boost version version bcm_setup_version(VERSION ${BOOST_CONFIG_VERSION}) add_library(boost_fusion INTERFACE) add_library(boost::fusion ALIAS boost_fusion) set_property(TARGET boost_fusion PROPERTY EXPORT_NAME fusion) bcm_boost_depends(boost_fusion INTERFACE boost_config boost_core boost_function_types boost_functional boost_mpl boost_preprocessor boost_static_assert boost_tuple boost_type_traits boost_typeof boost_utility ) bcm_install_targets(TARGETS boost_fusion INCLUDE include) bcm_auto_export(TARGETS boost_fusion)
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost