[OE-core] Automatically creating tar files for bin_package.bbclass

Andre McCurdy armccurdy at gmail.com
Tue Jul 5 08:21:17 UTC 2016


On Mon, Jul 4, 2016 at 8:58 AM, Burton, Ross <ross.burton at intel.com> wrote:
>
> On 4 July 2016 at 16:00, Andre McCurdy <armccurdy at gmail.com> wrote:
>>
>> Say I have a proprietary library which only I can build from source
>> and I have a conventional recipe which builds it within OE. I would
>> now like to create a tar file of the library and headers etc, plus a
>> companion recipe based on bin_package.bbclass to allow others to make
>> use of the library in their OE builds. ie the situation described
>> here:
>>
>> http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#packaging-externally-produced-binaries
>>
>> Is there a recommended way to create the tar file to support that?
>> e.g. a class which automatically creates a deployable tar file of a
>> recipe's ${D} directory?
>
> You *may* be able to use package_tar in the recipe in some way to achieve
> this.

It only seems to support creating tar files after packages have been
split ( ie individual tar files for each subdirectory under
${WORKDIR}/packages-split ). I don't think it's going to be directly
useful for creating a tar file of ${D}.

> Ross



More information about the Openembedded-core mailing list