id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
34	The kmk --jobs (-j) argument should default to the cpu/core count.	bird	bird	Most kBuild users (talking about actual developers here that are using it all day long) don't wish to have to  {{{SET/export KMK_FLAGS=-j2}}} in their environment. So, to make their life simpler, kmk should default the number of concurrent jobs to the number of cpus/cores in the system. For non-parallel building, {{{-j1}}} (or {{{--jobs=1}}} will do the trick.	enhancement	closed	major	0.1.4	kmk		fixed