Seconded. &nbsp;I once tried using bjam to build on an even slower machine, and never tried it again.<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 8:35 AM, Simon Pickles <span dir="ltr">&lt;<a href="mailto:sipickles@googlemail.com">sipickles@googlemail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Hi,<br>
<br>
Is there any way to make bjam only scan files for changes in the current working directory, rather than the whole boost installation? I hoped this would speed up the bjam build process. Everytime I do a build I get, for example:<br>

<br>
...patience...<br>
...patience...<br>
...found 2982 targets...<br>
...updating 6 targets...<br>
<br>
Wouldn&#39;t be quicker if it wasn&#39;t checking 3000 files each build? its a very slow machine you see! 900 MHZ!<br>
<br>
Thanks<br>
<br>
Simon<br>
<br>
-- <br>
Linux Counter: User# 424693 <br><font color="#888888">
<br>
<br>
<br>
-- <br>
Linux Counter: User# 424693 <br>
_______________________________________________<br>
Boost-users mailing list<br>
<a href="mailto:Boost-users@lists.boost.org" target="_blank">Boost-users@lists.boost.org</a><br>
<a href="http://lists.boost.org/mailman/listinfo.cgi/boost-users" target="_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-users</a><br>
</font></blockquote></div><br>