16 Jul
2009
16 Jul
'09
3 a.m.
On Wed, Jul 15, 2009 at 4:16 PM, Pete Bartlett
My main build machine is high-spec. I routinely use bjam -j N, but find that in the code that uses Boost most intensively, CPU is no longer the main determinant of compile time. Some source files take ~1GB of memory to compile - so trying to do several such files in parallel causes the meager 3GB or so of memory to be exhausted with all the problems that that entails. My /next/ build machine is not going to be constrained by the (Windows?) 32bit 4GB memory barrier!
At the risk of going off-topic, you can still use >4GB on a 32-bit Windows machine. The only catch is a single process can't use more than 2GB (or 3GB with some special work). -- Cory Nelson http://int64.org