Thanks for your helpful hints Ross !
I now have a script in place which:
- extracts package names from image manifest
- translates package names to recipe names
- grabs the source packages for those recipes (from what the archiver extracted
according to it’s config)
For two recipes, referenced b
Those recipes are special: the gcc-source recipe fetches and and
unpacks the GCC source tree, and gcc builds it. So gcc has no
source... Add gcc-source explicitly to your list and you'll be
sorted.
Ross
On Mon, 4 Feb 2019 at 16:23, David Zimmermann wrote:
>
> Thanks for your helpful hints Ross
Please remember to keep the list on CC.
The reason is that those recipes are built for the target so they'll
be archived, the archiver doesn't distinguish what recipes go into
what image.
It's relatively simple to filter the list after the build if you want
to produce just what is in a specific i
Does it not just contain the packages used to build the entire image,
so build-time dependents. Can you give an example of a recipe that is
archived but shouldn't be?
Ross
On Thu, 31 Jan 2019 at 08:46, David Zimmermann
wrote:
>
> Hi List,
>
> I use Yocto Krogoth and the following configuration
Hi List,
I use Yocto Krogoth and the following configuration for the archiver:
INHERIT += „archiver“
COPYLEFT_RECIPE_TYPES = ’target’
But the ‚tmp/deploy/sources/…/‚ folder for my target architecture contains much
more packages then those ‚used‘ to build my image.
Is there a way to extract / ar
