I always compile with jobs=1. ChunkSize has an effect on per-class 
build? There is something I don't understand.
It seems you are right on the memory. I saw swap usage increasing slowly 
while the compilation was stuck at "scons: Building targets ..." (no 
local diff after last compile attempt).
I didn't wait 100% swap though, after 30mins I wanted to work on the PC 
:-P . I stopped compilation at 75% swap or so.


p.s. Is it better to send this to [email protected] or to 
yade-dev? What do you prefer?

-- 
per-class build is broken?
https://bugs.launchpad.net/bugs/522244
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.

Status in Yet Another Dynamic Engine: New

Bug description:
This week-end, I fixed compile errors in per-class build. Now, I have no 
explicit error message, but the compilation still ends with "terminated because 
of errors"...
Can anybody compile "per-class" at the moment?
It seems monolithic takes more time for routine edit/compile on only one file. 
I spend most yade-time waiting for the compiler these days... it is annoying.



_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yade-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to