From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] local.conf.sample: Document memory resident bitbake
Date: Wed, 26 Aug 2020 00:19:34 +0100 [thread overview]
Message-ID: <7c1e1ad4adecd1e2faf0c4a9e96f1e25b3f65a6e.camel@linuxfoundation.org> (raw)
In-Reply-To: <162EA2592F13CDD9.27554@lists.openembedded.org>
On Tue, 2020-08-25 at 23:10 +0100, Richard Purdie via lists.openembedded.org wrote:
> Add an example of how to enable this to local.conf.sample
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> {meta => metay}/conf/local.conf.sample | 10 ++++++++++
> 1 file changed, 10 insertions(+)
> rename {meta => metay}/conf/local.conf.sample (96%)
>
> diff --git a/meta/conf/local.conf.sample b/metay/conf/local.conf.sample
> similarity index 96%
> rename from meta/conf/local.conf.sample
> rename to metay/conf/local.conf.sample
> index 783d2c4c16d..efb3100d9bd 100644
> --- a/meta/conf/local.conf.sample
> +++ b/metay/conf/local.conf.sample
> @@ -226,6 +226,16 @@ PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
> #BB_HASHSERVE = "auto"
> #BB_SIGNATURE_HANDLER = "OEEquivHash"
>
> +#
> +# Memory Resident Bitbake
> +#
> +# Bitbake's server component can stay in memory after the UI for the current command
> +# has completed. This means subsequent commands can run faster since there is no need
> +# for bitbake to reload cache files and so on. Number is in seconds, after which the
> +# server will shut down.
> +#
> +BB_SERVER_TIMEOUT = "60"
This is meant to have this commented, I've fixed the patches queued.
Cheers,
Richard
parent reply other threads:[~2020-08-25 23:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <162EA2592F13CDD9.27554@lists.openembedded.org>]
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=7c1e1ad4adecd1e2faf0c4a9e96f1e25b3f65a6e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox