On Tue, Feb 07, 2012 at 02:59:54PM +, McClintock Matthew-B29882 wrote:
The paths issue your are speculating on was fixed by myself and Richard last
November.
I would suggest running bitbake-diffsig to determine the actual sstate
differences.
Usually I'm complaining that sstate cache
On 02/06/2012 07:08 AM, Chris Larson wrote:
On Mon, Feb 6, 2012 at 12:53 AM, David Nyströmdavid.nyst...@enea.com wrote:
On 02/04/2012 05:51 AM, Scott Garman wrote:
Hello,
I'm trying to re-use the sstate from one build directory and move it to
another. It's not working - bitbake is
The paths issue your are speculating on was fixed by myself and Richard last
November.
I would suggest running bitbake-diffsig to determine the actual sstate
differences.
-M
On Feb 3, 2012 10:51 PM, Scott Garman
scott.a.gar...@intel.commailto:scott.a.gar...@intel.com wrote:
Hello,
I'm
On Mon, Feb 6, 2012 at 12:53 AM, David Nyström david.nyst...@enea.com wrote:
On 02/04/2012 05:51 AM, Scott Garman wrote:
Hello,
I'm trying to re-use the sstate from one build directory and move it to
another. It's not working - bitbake is rebuilding *everything*.
My hunch is the reason for
On 02/04/2012 05:51 AM, Scott Garman wrote:
Hello,
I'm trying to re-use the sstate from one build directory and move it to
another. It's not working - bitbake is rebuilding *everything*.
My hunch is the reason for this is because bblayers.conf must differ
between the two build directories,
Hello,
I'm trying to re-use the sstate from one build directory and move it to
another. It's not working - bitbake is rebuilding *everything*.
My hunch is the reason for this is because bblayers.conf must differ
between the two build directories, because it uses full paths to the
layer
