From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH] bitbake.conf: Start using parallel make for do_install
Date: Thu, 29 Sep 2011 11:06:30 -0700 [thread overview]
Message-ID: <1317319590.2134.0.camel@scimitar> (raw)
In-Reply-To: <1317308108.12332.92.camel@ted>
On Thu, 2011-09-29 at 15:55 +0100, Richard Purdie wrote:
> Most piece of software now support parallel make install. Enable
> this by default using the value of PARALLEL_MAKE. In a similar way
> to PARALLEL_MAKE we can disable this for broken recipes with:
>
> PARALLEL_MAKEINST = ""
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hurrah!
Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index f18e35b..a1420cf 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -493,8 +493,11 @@ export TARGET_LDFLAGS = "-Wl,-O1 ${TARGET_LINK_HASH_STYLE}"
> # Which flags to leave by strip-flags() in bin/build/oebuild.sh ?
> ALLOWED_FLAGS = "-O -mcpu -march -pipe"
>
> -# Pass parallel make options to the compile task only
> +# Pass parallel make options to the compile task
> EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} "
> +PARALLEL_MAKEINST ??= "${PARALLEL_MAKE}"
> +# Pass parallel make options to the install task
> +EXTRA_OEMAKE_prepend_task-install = "${PARALLEL_MAKEINST} "
>
> ##################################################################
> # Optimization flags.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-09-29 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 14:55 [RFC PATCH] bitbake.conf: Start using parallel make for do_install Richard Purdie
2011-09-29 18:06 ` Joshua Lock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1317319590.2134.0.camel@scimitar \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.