On 15/07/2015 19:35, Antony Polukhin wrote:
This is a recurring issue with boost libraries. Header only makes for a convenient library for many users - just include the header and try it out. On the other hand, for a large project where one is willing to invest more effort, a compiled library is attractive. I believe that for many libraries, it's possible to make the library such that one could have both by providing different #include for each type. This comment applies not to just this library but to others as well. Of course it wouldn't apply to all libraries. I would love to seem someone invest some effort to see if this is possible for this or some other library. Then if such an experiment were successful, we'd write up an article about it and include it in the boost body of work.
This could be useful. I'll think of adding a BOOST_DLL_USE_LIBRARY macro and compiling DLL as a library
Don't invent something new -- there's existing plumbing for this (see BOOST_ALL_DYN_LINK and friends). https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook#a16.BUILD:Conside...