From: Patrick Ohly <patrick.ohly@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: whatever happened to a proposal for "read-only" sstate?
Date: Fri, 03 Feb 2017 22:49:36 +0100 [thread overview]
Message-ID: <1486158576.14889.104.camel@intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1702031623390.12084@localhost.localdomain>
On Fri, 2017-02-03 at 16:24 -0500, Robert P. J. Day wrote:
> On Fri, 3 Feb 2017, Patrick Ohly wrote:
>
> > On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote:
> > > is there a command that will tell you how much shared state info a
> > > given build would be able to take advantage of?
> >
> > INHERIT += "buildstats-summary" in local.conf will print that
> > information after a build is done.
>
> but not before? ok, that will do for now.
It might do that also for a "bitbake --dry-run", but I am not sure, and
my build directory is currently busy, so I can't test it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-02-03 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:45 whatever happened to a proposal for "read-only" sstate? Robert P. J. Day
2017-02-03 14:18 ` Richard Purdie
2017-02-03 14:44 ` Robert P. J. Day
2017-02-03 19:14 ` Robert P. J. Day
2017-02-03 21:20 ` Patrick Ohly
2017-02-03 21:24 ` Robert P. J. Day
2017-02-03 21:49 ` Patrick Ohly [this message]
2017-02-04 17:12 ` Robert P. J. Day
2017-02-04 17:18 ` Robert P. J. Day
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=1486158576.14889.104.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.