https://svn.boost.org/trac10/ticket/10021 <p> Unlike other libraries, Boost.Interprocess doesn't use BOOST_USE_WINDOWS_H for Windows APIs. Instead, it declares used Windows APIs in boost/interprocess/detail/win32_api.hpp. The incompatible declares make some troubles in Clang and MinGW. Why not just regard to BOOST_USE_WINDOWS_H? </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10021 Trac 1.4.3 Minmin Gong <gongminmin@…> Thu, 08 May 2014 09:42:25 GMT https://svn.boost.org/trac10/ticket/10021 https://svn.boost.org/trac10/ticket/10021 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">boost_interprocess_use_windows_h.patch</span> </li> </ul> Ticket Ion Gaztañaga Wed, 28 May 2014 13:35:32 GMT https://svn.boost.org/trac10/ticket/10021#comment:1 https://svn.boost.org/trac10/ticket/10021#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">fixed</span> </li> </ul> <p> Thanks for the report and the patch. Inspired in your patch I committed to develop branch: </p> <p> SHA-1: de405e89a3208e6a12f617d730dc206eca25911a </p> <ul><li>If <code>BOOST_USE_WINDOWS_H</code> is defined, &lt;windows.h&gt; and other windows SDK files are included, </li></ul><p> otherwise the library declares needed functions and structures to reduce the impact of including those heavy headers. </p> <ul><li> Added <code>get_size</code> to windows_shared_memory. </li></ul> Ticket