Which does absolutely nothing. MAKE_JOBS has no effect on cmake.
The build is strictly sequential.
You can parallelize the bootstrap phase with
CONFIGURE_ARGS += --parallel=${MAKE_JOBS}
but the main build remains sequential so the overall gain is
negligible.
I haven't been able to figure
On Tue, Dec 11, 2012 at 7:59 PM, Amit Kulkarni amitk...@gmail.com wrote:
Which does absolutely nothing. MAKE_JOBS has no effect on cmake.
The build is strictly sequential.
You can parallelize the bootstrap phase with
CONFIGURE_ARGS += --parallel=${MAKE_JOBS}
but the main build remains
Which does absolutely nothing. MAKE_JOBS has no effect on cmake.
The build is strictly sequential.
You can parallelize the bootstrap phase with
CONFIGURE_ARGS += --parallel=${MAKE_JOBS}
but the main build remains sequential so the overall gain is
negligible.
I haven't been able
On Tue, Dec 11, 2012 at 01:22:27PM -0600, Amit Kulkarni wrote:
Which does absolutely nothing. MAKE_JOBS has no effect on cmake.
The build is strictly sequential.
You can parallelize the bootstrap phase with
CONFIGURE_ARGS += --parallel=${MAKE_JOBS}
but the main build remains
I tried with USE_GMAKE = Yes and it drives all cores
so I think please add CONFIGURE_ARGS = --parallel=${MAKE_JOBS} and
USE_GMAKE = Yes and then both configure and build will go parallel.
Please just let me know what should I do, because I know nothing about
DPB and
On Tue, 11 Dec 2012, Brad Smith wrote:
The use of GNU make like this seems bogus. I take it CMake
isn't doing something right.
Hi,
I've found another (related) problem.
$MAKE_PROGRAM is not honored and cmake picks gmake up if it's
installed (even without USE_GMAKE=Yes).
From
