gbuild: GMAKE_OPTIONS overridable ...

Bjoern Michaelsen bjoern.michaelsen at
Mon Apr 30 03:12:50 PDT 2012

On Mon, Apr 30, 2012 at 10:28:09AM +0200, Tomáš Chvátal wrote:
> Splendid so I will just drop the max-jobs one.
> Now we have the GMAKE_OPTIONS that affect gbuild and --with-num-cpus that 
> affects dmake right? Or they still kinda collide with each other?

They still collide below tail_build although that is a part of the build that
is getting smaller and smaller as stuff gets merged into tail_build. Below
- kicks of ${--with-num-cpus} processes of dmake/gmake
- the dmake processes spawn ${--with-max-jobs} processes each
- the gmake processes spawn ${--with-max-jobs} processes each, unless
  overridden by GMAKE_OPTIONS

So there you might still end up with max-jobs*num-cpus jobs running in

In tail_build itself everything is sane:
- it builds with the the higher value of num-cpus, max-jobs -- unless
  overridden by GMAKE_OPTIONS

Once everything is in tail_build, num-cpus and max-jobs and GMAKE_OPTIONS can
be removed and we simply take what was given on the commandline. So migrate to
gbuild, for the greater good of everyone!



More information about the LibreOffice mailing list