<HTML><HEAD><!-- Template generated by Exclaimer Mail Disclaimers on 08:35:43 woensdag, 24 augustus 2016 -->
<STYLE type=text/css>P.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
LI.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
DIV.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
TABLE.ImprintUniqueIDTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY>
<P class=ImprintUniqueID><div>On 23-08-16 17:32, Richard Purdie wrote:<br />> On Tue, 2016-08-23 at 15:15 +0000, Peter Kjellerstedt wrote:<br />>> This is the first I heard about limits to recipes that inherit<br />>> allarch<br />>> and also use RDEPENDS. So after I read the above, I went and read the<br />>> documentation for the allarch class, which unfortunately did not make<br />>> my understanding much clearer.<br />>><br />>> Am I to understand that a recipe that inherits allarch cannot have<br />>> runtime dependencies on packages that are built differently per<br />>> architecture or MACHINE? If so, what can it have runtime dependencies<br />>> on? Only other allarch recipes? What are the design limitations<br />>> behind this and is there anything that could be done to change the<br />>> situation?<br />><br />> It can depend on them, only if you add it to the list of dependencies<br />> in layer.conf, either SIGGEN_EXCLUDERECIPES_ABISAFE or<br />> SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS. The implication of that is that if<br />> one of these recipes changes, the dependency will not be rebuilt, so<br />> you have to be careful about things like these packages getting<br />> renamed.<br />><br />> Its basically a choice, we can have allarch packages and accept we<br />> can't always rebuild them through the sstate hash changes, or we don't<br />> have allarch packages at all (or have packages that can't have non<br />> -allarch dependencies).<br /><br />First time I've heard about this limitation, I don't understand what's this <br />about either. I've been telling people to put their arch or machine specific <br />code into a seperate package and RDEPEND on it from an allarch package that <br />holds the Python code that calls into that.<br /><br />We haven't seen any problems with that.<br /><br />So what is the bad thing that would happen if we don't set the <br />SIGGEN_EXCLUDE... variables in the layer.conf file?<br /><br />>> As an example, say that I have a recipe that only installs a static<br />>> script, so inheriting allarch is a natural thing to do. However, for<br />>> this script to work it must call a binary built by another recipe so<br />>> it of course RDEPENDS on that other package. Are you saying this is<br />>> wrong? Because that sounds odd to me as it severely limits the<br />>> usefulness of the allarch class.<br />><br />> You can do this if and only if you list it in layer.conf.<br />><br />>> Another example would be a recipe that installs a static Perl script.<br />>> Can it not inherit allarch while also have a runtime dependency on<br />>> perl?<br />>><br />>> If the above is true, why are there no QA tests or similar that catch<br />>> these kind of problems?<br />><br />> We do have sstate hash tests in oe-selftest which would highlight such<br />> a problem.<br />><br />> There are various open bugs complaining about this situation however<br />> I've yet to come up with a way which solves the problem perfectly, much<br />> as I'd like to.<br /><br />I'm totally in the dark as to what should go where now.<br /><br />Given the situation above, a recipe called "static-perl-script.bb" that <br />requires the "perl" interpreter, what should we put into layer.conf then?<br /><br /><br /><br /></div></P>
<P class=ImprintUniqueID><FONT face="Calibri Light"></FONT> </P>
<P class=ImprintUniqueID><FONT face="Calibri Light">Kind regards,</FONT></P>
<P class=ImprintUniqueID><FONT face="Calibri Light"></FONT> </P>
<P class=ImprintUniqueID><font style='font-family:Calibri Light;font-size:12pt;font-weight:bold;'>Mike Looijmans</font></P>
<P class=ImprintUniqueID><font style='font-family:Calibri Light;font-size:12pt;'>System Expert</font></P>
<P class=ImprintUniqueID><FONT face="Calibri Light"></FONT> </P>
<P class=ImprintUniqueID><FONT face="Calibri Light"></FONT></P>
<P class=ImprintUniqueID><FONT face="Calibri Light"></FONT></P>
<P class=ImprintUniqueID><img width=375 height=74 style='border: 0px Solid ; 'src="cid:imagef3bd97.PNG@bc10c9c1.4e9da1a5"><BR /><BR /></P>
<P class=ImprintUniqueID>
<TABLE class=ImprintUniqueIDTable style="HEIGHT: 72px; BORDER-COLLAPSE: collapse; WIDTH: 475px" cellSpacing=0 cols=3 cellPadding=0 border=0>
<TBODY>
<TR>
<TD style="WIDTH: 205px">
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"><STRONG>TOPIC
Products</STRONG></FONT></P></TD>
<TD style="WIDTH: 6px">
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"></FONT> </P></TD>
<TD style="WIDTH: 256px">
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"></FONT> </P></TD></TR>
<TR>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">Materiaalweg
4</FONT></P></TD>
<TD style="WIDTH: 29px">
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"></FONT> </P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"></FONT> </P></TD></TR>
<TR>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">5681
RJ Best</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">T:</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">+31 (0) 499 33
69 69</FONT></P></TD></TR>
<TR>
<TD style="HEIGHT: 14px">
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">Postbus
440</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">E:</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><font style='font-family:Calibri Light;font-size:8pt;'>mike.looijmans@topicproducts.com</font></P></TD></TR>
<TR>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">5680 AK
Best</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light">W:</FONT></P></TD>
<TD>
<P class=ImprintUniqueID><FONT size=1 face="Calibri Light"><A href="http://www.topicproducts.com">www.topicproducts.com</A></FONT></P></TD></TR>
<TR>
<TD><FONT size=1 face="Calibri Light">The Netherlands</FONT></TD>
<TD><FONT size=1 face="Calibri Light"></FONT></TD></TD>
<TD><FONT size=1 face="Calibri Light"></FONT></TD>
<TD><FONT size=1 face="Calibri Light"></FONT></TD></TR></TBODY></TABLE></P>
<P class=ImprintUniqueID><A href="https://www.facebook.com/TopicProducts"><FONT size=1 face="Calibri Light"><IMG id=IMG1 border=0 src="cid:imagecb41f7.JPG@0860e157.47b37f5d" width=20 height=19 /> </FONT></A><A href="https://twitter.com/TopicProducts"><FONT size=1 face="Calibri Light"><IMG id=IMG1 border=0 src="cid:image1bf521.JPG@00b0c1ee.4a8eb291" width=20 height=19 /></FONT></A><A href="https://www.linkedin.com/company/topic-embedded-products"><FONT size=1 face="Calibri Light"><IMG id=IMG1 border=0 src="cid:image988d3a.JPG@2742c28a.409d0397" width=20 height=18 /></FONT></A><BR /><FONT color=green size=1 face="Calibri Light">Please consider the environment before printing this
e-mail<BR /></FONT></P><BR /><A href="http://topic.nl/vacancy/topic-zoekt-technische-software-engineers/"><font style='font-family:Arial;font-size:8pt;'>Topic zoekt gedreven (embedded) software specialisten!</font></A><BR /><BR />
<P class=ImprintUniqueID></P>
<P><FONT face="Calibri Light"></FONT></P>
<P><FONT face="Calibri Light"></FONT></P></FONT></EM></BODY></HTML>