<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Hi Khem,<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">On Fri, Jun 1, 2018 at 1:11 PM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 5/31/18 1:06 PM, Trevor Woerner wrote:<br>
> Instead of installing an entire recipe's build output (i.e. ${D}), allow the<br>
> user to optionally specify a package from said recipe to be installed<br>
> exclusively (i.e. ${PKGDEST}/<package>).<br>
> <br>
<br>
</span>Thinking of developer's workflow, it might be needed to be able to<br>
install debug/dev packages to debug the package on device.<br>
<br>
although I think we should be able to segment it and may be have an<br>
option to install the dev part separately<br></blockquote><div><br></div><div>Currently -dev packages will be installed, but -dbg packages will not (since the components of the -dbg package aren't placed in ${D}). So if anything this patch (or better yet, the v2 I'll be sending shortly) will improve the situation.</div><div><br></div><div>Although I have noticed that there are differences between the -dbg package that is created with the normal bitbake workflow and the -dbg package that is created as part of the "devtool modify ..." workflow.<br></div></div></div></div>