https://svn.boost.org/trac10/ticket/12883 <p> We are trying to use Boost/config in the API of our library -- it really helps for exporting symbols/etc. But that means we need to ship those files as we cannot assume the library consumer has Boost installed. So our API is organized like this: </p> <p> include/ </p> <ul><li> my_library.h (This has #include "config.hpp" _relative_ import) </li><li> config.hpp </li><li> config/ </li><li> ... </li></ul><p> This is fine and works great when we are building the library. But since config uses &lt;&gt; when #include'ing everything below it, consumers need to add the path to the include search path. I feel the use of Boost/config should be an implementation detail of my API that the consumer is not required to know. I would like to see config use relative paths instead of system paths. </p> <p> I dug up <a class="new ticket" href="https://svn.boost.org/trac10/ticket/12063" title="#12063: Bugs: boost include directives use double quotes incorrectly (new)">#12063</a> and <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/12064" title="#12064: Bugs: boost include directives use double quotes incorrectly (closed: fixed)">#12064</a>, but those were more interested in making #include work instead of fixing the relative paths. I understand that other parts of Boost need to properly find everything else in Boost, but config seems isolated to only itself; i.e. relative paths should not interfere with the local project files. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12883 Trac 1.4.3 John Maddock Tue, 31 Jul 2018 18:40:06 GMT https://svn.boost.org/trac10/ticket/12883#comment:1 https://svn.boost.org/trac10/ticket/12883#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> Ticket