<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 July 2016 at 16:00, Andre McCurdy <span dir="ltr"><<a href="mailto:armccurdy@gmail.com" target="_blank">armccurdy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":lr" class="a3s aXjCH m155b66d756d8ea95">Say I have a proprietary library which only I can build from source<br>
and I have a conventional recipe which builds it within OE. I would<br>
now like to create a tar file of the library and headers etc, plus a<br>
companion recipe based on bin_package.bbclass to allow others to make<br>
use of the library in their OE builds. ie the situation described<br>
here:<br>
<br>
<a href="http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#packaging-externally-produced-binaries" rel="noreferrer" target="_blank">http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#packaging-externally-produced-binaries</a><br>
<br>
Is there a recommended way to create the tar file to support that?<br>
e.g. a class which automatically creates a deployable tar file of a<br>
recipe's ${D} directory?</div></blockquote></div><br>You *may* be able to use package_tar in the recipe in some way to achieve this.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>