On Wed, 2016-08-24 at 08:35 +0200, Mike Looijmans wrote: > First time I've heard about this limitation, I don't understand > what's this about either. I've been telling people to put their arch > or machine specific code into a seperate package and RDEPEND on it > from an allarch package that holds the Python code that calls into > that. > > We haven't seen any problems with that. > > So what is the bad thing that would happen if we don't set the > SIGGEN_EXCLUDE... variables in the layer.conf file?
If you have an allarch recipe X and you depend on a tune or machine specific package from it, what you'll see is that when you switch MACHINE (with a different tune), the recipe X will rebuild each time. This is obviously suboptimal however its not the end of the world. It is problematic if you're using PR server. The reason it rebuilds is that its checksum has a dependency on something which is tune or machine specific, you change MACHINE, the checksum changes and the allarch recipe's checksum changes. If we remove the dependency from the task checksum, the problem isn't there and it doesn't rebuild, however there are some circumstances where this could be an issue, e.g. if a dependency name was renamed by debian.bbclass for example. The mechanism for removing such a dependency is the one I've mentioned in layer.conf. You can see if you have a problem with your layers by running: oe-selftest -r sstatetests.SStateTests.test_sstate_allarch_samesigs Does that make the issue any clearer? Related bugs: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7298 https://bugzilla.yoctoproject.org/show_bug.cgi?id=8078 https://bugzilla.yoctoproject.org/show_bug.cgi?id=7724 Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
