Boost C++ Libraries: Ticket #2433: bjam should honor include paths order https://svn.boost.org/trac10/ticket/2433 <p> Currently bjam does not honor include paths and sorts things alphabetically as an speed optimization (I believe it has to do with comparing sets of paths for equivalence). In reality, bjam should honor include path order not only within a &lt;include&gt; attribute but also within a project hierarchy itself. </p> <p> Here is a great thread with a lot of good discussion about the issue and what I have in mind for bjam: </p> <p> <a class="ext-link" href="http://www.nabble.com/Sorting-include-headers-td19995752.html"><span class="icon">​</span>http://www.nabble.com/Sorting-include-headers-td19995752.html</a> </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2433 Trac 1.4.3 René Rivera Sat, 25 Oct 2008 15:16:05 GMT owner, version, component changed https://svn.boost.org/trac10/ticket/2433#comment:1 https://svn.boost.org/trac10/ticket/2433#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">René Rivera</span> to <span class="trac-author">Vladimir Prus</span> </li> <li><strong>version</strong> <span class="trac-field-old">Boost 1.36.0</span> → <span class="trac-field-new">Boost Development Trunk</span> </li> <li><strong>component</strong> <span class="trac-field-old">bjam</span> → <span class="trac-field-new">build</span> </li> </ul> Ticket anonymous Wed, 23 Nov 2011 15:37:03 GMT <link>https://svn.boost.org/trac10/ticket/2433#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2433#comment:2</guid> <description> <p> This is indeed a very good proposal. I am currently finding myself with the problem that a particular path NEEDS to be included before another one, and there is just no way that this works with bjam, is there? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Vladimir Prus</dc:creator> <pubDate>Wed, 23 Nov 2011 17:54:25 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2433#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2433#comment:3</guid> <description> <p> There is, just put: </p> <pre class="wiki">&lt;include&gt;a&amp;&amp;b </pre><p> in requirements for relevant metatarget or project. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Steven Watanabe</dc:creator> <pubDate>Wed, 23 Nov 2011 18:15:23 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2433#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2433#comment:4</guid> <description> <p> Unfortunately, this isn't completely foolproof. Given, &lt;include&gt;b&amp;&amp;a &lt;include&gt;a we'll end up with a b a. </p> <p> It would work better if we used a topological sort. Isn't there already something like this for libraries? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Vladimir Prus</dc:creator> <pubDate>Wed, 23 Nov 2011 18:49:55 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2433#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2433#comment:5</guid> <description> <p> Hmm, I swear the plan was to put values with "&amp;&amp;" to the front of the list, before splitting, but I cannot see the evidence this is actually done in the current code. </p> <p> topological sort would work. another alternative, of course, it just don't sort include properties, but the performance consequences of that are still uncearl. </p> </description> <category>Ticket</category> </item> </channel> </rss>