
Is there a quicker alternative? Trouble is I've only just got to grips with jam files! ------------------------------------------------------------------------ Seconded. I once tried using bjam to build on an even slower machine, and never tried it again.
------------------------------------------------------------------------
Subject: Speed up bjam From: Simon Pickles
Date: Tue, 18 Nov 2008 13:35:03 +0000 To: boost-users@lists.boost.org To: boost-users@lists.boost.org
Hi,
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:
...patience... ...patience... ...found 2982 targets... ...updating 6 targets...
Wouldn't be quicker if it wasn't checking 3000 files each build? its a very slow machine you see! 900 MHZ!
Thanks
Simon

Simon Pickles wrote:
Is there a quicker alternative? Trouble is I've only just got to grips with jam files!
Not right now. Python port of Boost.Build is likely to be somewhat faster (a fairly artificial test focusing on Boost.Build proper was 10x faster). - Volodya
participants (2)
-
Simon Pickles
-
Vladimir Prus