On 09/18/2014 12:21 AM, Otavio Salvador wrote:
On Wed, Sep 17, 2014 at 1:16 PM, Richard Purdie
<[email protected]> wrote:
On Wed, 2014-09-17 at 16:08 +0800, Hongxu Jia wrote:
The idea of incremental sig is:
New sig file = Old sig file (if available) + New sig items in current build.
Limit the modification within the dump_lockedsigs, and add two variables
'self.lockedsigs_types' and 'self.lockedsigs_raw' keep old sig file.
How to config for incremental dump:
...
USER_CLASSES += "sstate_lockedsig"
SIGGEN_LOCKEDSIGS_CONFIG = "${TOPDIR}/locked-sigs.inc"
require ${SIGGEN_LOCKEDSIGS_CONFIG}
...
Signed-off-by: Hongxu Jia <[email protected]>
I'm fine with the idea in principle. Why can't we do something like:
...
which is substantially simpler though?
Wouldn't it keep accumulating locked hashes for same recipes?
Of course not, checking added before write to file
...
+ if pn in self.lockedsigs and task in self.lockedsigs[pn]
and self.hashtask[k] == self.lockedsigs[pn][task]:
+ continue
...
But there are still accumulating empty SIGGEN_LOCKEDSIGS added, such as:
...
SIGGEN_LOCKEDSIGS_t-x86-64 += "\
"
SIGGEN_LOCKEDSIGS_TYPES_qemux86 += "t-x86-64"
...
I will fix it in V3
//Hongxu
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
