On Sun, 2014-01-05 at 17:55 +0100, Kalrish Bäakjen wrote:
> Hello,
>
> Some projects (e.g., mpv, in community) are moving from Autotools to other
> build systems. I think we should create a JOBS variable indicating the
> number of parallel jobs, leaving MAKEFLAGS for make-specific options. We
> could also implement SCONSFLAGS, WAFFLAGS,… although that may be a bit
> premature.
>
> The reason behind this is that a given build system might not understand
> "-j N". (And, also, for SCons projects, the "-Q" flag could be desired.)
>
> In the proposed model, each PKGBUILD would appropiately tell the build
> system how many jobs to do in parallel, or ignore the setting.
>
> As an extra question, may I ask why aren't MAKEFLAGS used in official
> PKGBUILDs? I mean, as in:
> make ${MAKEFLAGS}
> Perhaps make automatically fetches options from the environment? Or maybe
> because package construction is automated in a server and other processes
> are running in other cores?
>
> Thanks,
> Kalrish
Salutations,
Forgive me if I misunderstood, but isn't Makeflags specified in the
MAKEFLAGS array in makepkg.conf (see
<https://wiki.archlinux.org/index.php/Makepkg#MAKEFLAGS>). They should
be automatically fetched from the environment.
Regarding your idea for supporting different build tools, I think
officially Arch supports the build tools provided in base-devel (which
would be autotools). While there are distcc flags (not in base-devel
group) in makepkg, a change in makepkg.conf would probably reflect a
change in the base-devel group (like adding waf).
Regards,
Mark
--
Mark Lee <mark@xxxxxxxxxxxxx>
Attachment:
signature.asc
Description: This is a digitally signed message part
