On Fri, Dec 12, 2008 at 12:33 AM, Christian Ehrlicher <span dir="ltr"><<a href="mailto:Ch.Ehrlicher@gmx.de" target="_blank">Ch.Ehrlicher@gmx.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Patrick Spendrin schrieb:<div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
as I am just working with some boost headers that do reside in a different include directory, I would like to ask to apply the appended patch.<br>
It will not only find versions where headers are in prefix/include/boost/boost_1_34 (which is currently the default for windows) but also prefix/include/boost/boost-1_34 (as it is currently on non-Win32 platforms).<br>
The patch would only lead to unwanted effects if somebody is using the difference between win32 and non-win32 versions currently (e.g. he has boost-1_34 and boost_1_34 in the same directory). As this seems to strange to be used, I'd think the patch is safe enough to be applied.<br>
<br>
</blockquote></div>
There's an open bug to fix this here: <a href="http://public.kitware.com/Bug/view.php?id=8173" target="_blank">http://public.kitware.com/Bug/view.php?id=8173</a><br>
<br>
But no reaction so far...</blockquote><div><br>Obviously many bugs in the tracker aren't getting dealt with (don't know why). Perhaps Kitware should recruit some more people to help with triage? There are 83 in the new state at the current time. Obviously Boost issues are falling through the cracks along with many other bugs. :(<br>
</div></div><br>-- <br>Philip Lowman<br>