On Wed, Dec 12, 2012 at 12:48:09PM +0100, David Coppa wrote:
> On Tue, 11 Dec 2012, Amit Kulkarni wrote:
>
> > >> > > 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.
> > >> > >
>
> ...
>
> > > The use of GNU make like this seems bogus. I take it CMake
> > > isn't doing something right.
> >
> > as far back as 2008 I seem to remember cmake having implicit
> > dependency on gmake (i tried it on on Solaris,FreeBSD and then
> > OpenBSD). my builds would always parallel build with gmake but not
> > with plain os make. i still haven't figured out why. maybe david can
> > chime in with more...
> >
> > perhaps
> > http://cmake.3232098.n2.nabble.com/parallel-make-j-N-td7193296.html
> >
> > which leads to
> > http://public.kitware.com/Bug/view.php?id=12882
>
> Hi again,
>
> Since I've tried all the weapons in my arsenal and found nothing
> useful, I think I can be ok with Amit's approach.
>
> I did the usual tests and it doesn't seem to introduce any regressions
> after all...
>
> Summarizing:
>
> I've added "--parallel=${MAKE_JOBS}".
>
> Added "--verbose" that prints some nice informations, like
>
> System: OpenBSD
> Doing parallel make: 2
>
> Removed USE_GROFF which is not needed.
>
> Added a "XXX" to the comment.
>
> Thoughts? OKs?
USE_GMAKE is _not_ the way to go. What next, add USE_GMAKE to all ports
using cmake ? Our make -j itself works, one just need to find why cmake
doesnt take benefit from it.
Landry
