On Thu, Nov 25, 2010 at 4:44 PM, Cristian Oneţ <onet.crist...@gmail.com> wrote: > On Thu, Nov 25, 2010 at 5:38 PM, Andre Heinecke <aheine...@intevation.de> > wrote: >> Hi, >> >> Am Sonntag, 7. November 2010 23:00:25 schrieb Patrick Spendrin: >>> Ok, binaries from Christian have been uploaded & a new emerge target has >>> been added: >>> Please retry emerge -i --target=101-patched jom >> >> To give feedback here, the new version thats default now works great, it >> reduced our build times with msvc ~20%. >> >> Had a strange Problem with mingw though, during a large qt build i've killed >> emerge with control C and jom just kept building it although emerge and the >> controlprocess was dead. >> >> When a build breaks i get the message (this is with msvc): >> QProcess: Destroyed while process is still running. >> >> command failed with exit code 2 >> >> command failed with exit code 2 >> >> command failed with exit code 2 >> emerge fatal error: while running make cmd: jom.exe -j8 VERBOSE=1 > > Could you provide a short description on how to use jom (or a link to > where is this described)? I have emerged jom but make only launches > one compiler process.
Jom normally auto-detects the amount of CPU's in the system and uses this amount as its amount of jobs. I believe I set EMERGE_MAKE_PROGRAM to also append the amount of jobs and silent mode. I'm not at home right now, but I believe my EMERGE_MAKE_PROGRAM is: EMERGE_MAKE_PROGRAM=%KDEROOT%\dev-utils\bin\jom.exe -j8 -s _______________________________________________ Kde-windows mailing list Kde-windows@kde.org https://mail.kde.org/mailman/listinfo/kde-windows
