04:38 <testuser[m]> Hi

07:23 <sewn> 🐈

11:01 <GoatAvenger> does 'kiss b suchandsuch' build with multiple-threads by default, or does it only build with a single thread? and if only a single threads, is there some way to have builds be multi-threaded?

14:30 <davidgarland> GoatAvenger: put "export MAKEFLAGS=-jN" into your ~/.profile, where N is the number of threads your CPU has

14:31 <davidgarland> I think cargo might use multiple threads by default, unsure

14:31 <davidgarland> but for C that's what you need

14:33 <GoatAvenger> davidgarland, that will cover ninja builds and cmake builds as well? (if I'm making sense)

14:34 <davidgarland> yeah, I believe so-- haven't had any builds that seemed like they were running single threaded under those

14:34 <GoatAvenger> sweeeet, thnx a lot

14:38 <davidgarland> it looks like samurai (the library that supplies ninja) just always uses the max number of available threads when deciding how many jobs to do? https://github.com/michaelforney/samurai/blob/2d05a9ac47794131efeb59e7dc4ee99287738c9c/parse.c#L194

14:38 <davidgarland> well, there's some more complicated "load average" thing they mention but basically it seems like it might just ignore MAKEFLAGS and always run multiprocess

14:39 <davidgarland> either way no cause for concern

14:39 <testuser[m]> davidgarland: SAMUFLAGS=-jN

14:39 <davidgarland> aa nice

14:39 <davidgarland> does that make a difference in your experience?

14:40 <testuser[m]> It uses that lol

14:40 <testuser[m]> i use ti for chromium

14:40 <davidgarland> what I mean is

14:40 <davidgarland> is it noticably faster than the default number of jobs it picks

14:41 <davidgarland> because the bit I linked seems to suggest they try to auto detect that

14:43 <testuser[m]> i use it. To limit not increase

14:44 <davidgarland> gotcha

14:44 <GoatAvenger> I did look into it previous; if my understanding is correct, ninja uses max by default. Thnx for extra info testuser[m]; that helps too.

14:44 <GoatAvenger> Many thnx testuser[m], davidgarland.