<div class="gmail_quote">On Mon, Jan 9, 2012 at 14:26, Mark Hatle <span dir="ltr"><<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 1/9/12 2:09 AM, Phil Blundell wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You could take a look at the busybox-config.inc stuff in oe-classic as a<br>
starting point. It doesn't do PACKAGECONFIG (since oe-classic doesn't<br>
have that) but it can do the equivalent with DISTRO_FEATURES.<br>
</blockquote>
<br></div>
At Wind River we've discussed using the kernel configuration fragment patching process as a way to control busybox. This would allow the recipe to provide a default fragment (configuration), with machines, architectures, and other configurations providing additional fragments -- that together would produce the busybox that the end use wants.<br>
<br>
I think this is a better long term approach then hacking the defconfig file each time it's not quite right for a system. (We may still need to modify it over time, but the modifications need to be considered "generic" based on the use of busybox in say core-image-minimal...)</blockquote>
<div><br></div><div>I agree with the concept of the idea and long term solution however I also think it needs to be well documented otherwise it is going to be a problem, instead of a solution.</div><div><br></div><div>When I tried to use the kernel configuration fragment from Yocto I couldn't figure it out by myself and it seems very undocumented thus its learn curve is not as good as I'd hope for...</div>
<div> </div></div>-- <br>Otavio Salvador O.S. Systems<br>E-mail: <a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a> <a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a><br>
Mobile: +55 53 9981-7854 <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br><br>