[yocto] Building single package as image, respecting dependencies
Norman Stetter
Norman.Stetter at garz-fricke.com
Wed May 29 06:30:28 PDT 2019
Hello Paul,
thank you for your suggestion. I will look into it.
Meanwhile I worked around my issue by building all python3 packages, but excluding them from the rootfs. Then they get installed into a separate 'rootfs', which I pack as a squashfs image.
It might not be that elegant, but it works.
Regards,
NOrman
Mit freundlichen Grüßen / Best regards
Norman Stetter
SW ENWICKLUNG EMBEDDED SYSTEMS
Garz & Fricke GmbH
21079 Hamburg
Direct: +49 40 791899 - 477
Fax: +49 40 791899 - 39
Norman.Stetter at garz-fricke.com
www.garz-fricke.com
WE MAKE IT YOURS!
Sitz der Gesellschaft: D-21079 Hamburg
Registergericht: Amtsgericht Hamburg, HRB 60514
Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
> -----Ursprüngliche Nachricht-----
> Von: Paul Barker [mailto:paul at betafive.co.uk]
> Gesendet: Tuesday, May 28, 2019 11:37 AM
> An: Norman Stetter <Norman.Stetter at garz-fricke.com>; Burton, Ross
> <ross.burton at intel.com>
> Cc: yocto at yoctoproject.org
> Betreff: Re: [yocto] Building single package as image, respecting
> dependencies
>
> On 24/05/2019 15:28, Norman Stetter wrote:
> > Is there no way to simply force bitbake to only build the packages I
> > want, ignoring dependencies? We used to build the image like this
> > before, using PTXDist.
> >
> > Everything else seems to be a dirty hack.
>
> Can you just collect the extra packages (ipk/deb/rpm as appropriate), put
> them in a package feed and install them on-target as required?
>
> The package feed doesn't have to be on a webserver, you could put it in a
> directory in a separate partition on the target if that's what you need.
>
> Thanks,
>
> --
> Paul Barker
> Managing Director & Principal Engineer
> Beta Five Ltd
More information about the yocto
mailing list