public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: Balasubramanian Sundaram <balasubramanian.sundaram@sanmina.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: Removing unused binaries from ISAR final .wic .image
Date: Thu, 22 Sep 2022 08:36:27 +0000	[thread overview]
Message-ID: <AM9PR10MB486904A8563F9A3CD34081DE894E9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <7afd8964-52b9-43d9-9cee-4326a99827c9n@googlegroups.com>

> From: 'Balasubramanian Sundaram' via isar-users <isar-users@googlegroups.com> 
> Sent: Thursday, September 22, 2022 8:59 AM
> To: isar-users <isar-users@googlegroups.com>
> Subject: Re: Removing unused binaries from ISAR final .wic .image
> 
> Hi  Team,
> 
> we are use ISAR build system for imx6 NXP Based Processor, In which we need to remove unused binaries to reduce the rootfs size (optimisation),
> we need to remove binaries like 
> libx11-6
> shared-mime-info
> Perl
> dbus
> gpg 
> can you please help in which file inside ISAR build system we need to to do modification to remove these binaries in the final .wic.image
> and also provide the procedure steps to remove it in the final .wic.image

Hi,

Some of the are probably transitive dependencies of your own packages (or packages you install).
For example, dbus, libx11-6 and shared-mime-info are not essential packages.
To analyze this, I recommend to use "apt rdepends", e.g. via "apt rdepends libx11-6".

For essential packages, you can manually uninstall them by adding a custom bitbake task to ROOTFS_POSTPROCESS_COMMAND.
There you can chroot into the buildchroot and issue something like "apt remove -y --allow-remove-essential <package>".
Using that pattern, you could even remove apt as a last step.

For details, have a look in the rootfs.bbclass [1].

BTW: These packages technically removed from the rootfs which is an input to wic to generate the final (bootable) image.

[1] https://github.com/ilbers/isar/blob/master/meta/classes/rootfs.bbclass#L232

Best regards,
Felix

> 
> Thanks & Regards


      reply	other threads:[~2022-09-22  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  6:59 Balasubramanian Sundaram
2022-09-22  8:36 ` Moessbauer, Felix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM9PR10MB486904A8563F9A3CD34081DE894E9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=balasubramanian.sundaram@sanmina.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox