All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Abhi Arora <abhiarora4@live.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Reducing the size of the image by optimizing python
Date: Fri, 18 Oct 2019 14:28:23 +0530	[thread overview]
Message-ID: <CAMKF1sofAn-D104y=Aj2SQuvjrnLqoQjcpRRL3oNjTrXw75d3w@mail.gmail.com> (raw)
In-Reply-To: <MAXPR01MB220688520F47DEEC5D530BD9FA6C0@MAXPR01MB2206.INDPRD01.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

On Fri, Oct 18, 2019 at 1:21 PM Abhi Arora <abhiarora4@live.com> wrote:

> Hello,
> I am having an embedded system. We have bsp with python 3.5 but we want to
> reduce its size further. I am planning to have only oyc files but not sure
> how it can be achieved in recipes. Also, I want to know if there is a other
> way to reduce the footprint.
>

Please start by eliminating modules first so find which modules are
required for your workloads and remove all other modules from image by
adding them to BAD_RECOMMENDATIONS from IMAGE_INSTALL

>
>
> Please help.
>
> Get Outlook for Android <https://aka.ms/ghei36>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2370 bytes --]

  reply	other threads:[~2019-10-18  8:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:49 Reducing the size of the image by optimizing python Abhi Arora
2019-10-18  8:58 ` Khem Raj [this message]
2019-10-19 12:45   ` Abhi Arora
2019-10-19 14:34     ` Richard Purdie
2019-10-19 14:55       ` Abhi Arora
2019-10-19 15:10         ` richard.purdie
2019-10-19 15:21           ` Yann Dirson
2019-10-19 16:32             ` Abhi Arora
2019-10-20 10:59               ` Josef Holzmayr
2019-10-20 15:29                 ` Abhi Arora
     [not found]           ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.4240ac9c-b01f-45e6-9070-5b2736653819@emailsignatures365.codetwo.com>
     [not found]             ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.bf5d2683-0b1e-4651-b4bc-cad3e441cbf0@emailsignatures365.codetwo.com>
2019-10-21 11:50               ` Mike Looijmans
2019-10-21  9:09     ` Ross Burton

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='CAMKF1sofAn-D104y=Aj2SQuvjrnLqoQjcpRRL3oNjTrXw75d3w@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=abhiarora4@live.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.