From: Yann Dirson <yann.dirson@blade-group.com>
To: richard.purdie@linuxfoundation.org
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Reducing the size of the image by optimizing python
Date: Sat, 19 Oct 2019 17:21:52 +0200 [thread overview]
Message-ID: <CA+4=imYxNpiox1pPwi52LeL56vT+ZSpFgj9EStYh+EXmirBNeA@mail.gmail.com> (raw)
In-Reply-To: <e6d9c7aa1796070677b20b08999fa2313abde740.camel@linuxfoundation.org>
You can also look at the package dependency graph (see the file
generated by bitbake -g) to get a better idea of what pulls what.
2019-10-19 17:10 UTC+02:00, richard.purdie@linuxfoundation.org
<richard.purdie@linuxfoundation.org>:
> On Sat, 2019-10-19 at 14:55 +0000, Abhi Arora wrote:
>> Thanks your for the suggestion.
>>
>> From where I can find out what modules and packages python3-misc
>> downloads and installs? I am new to yocto and Don't know where to
>> look for. I tried grep but didn't help me.
>
> python3-misc is a package. You can look at its dependencies to see what
> it adds to the image.
>
>> And how about optimization using pyc file? Is it doable?
>
> Start simple. If you have python3-misc installed its using a lot of
> space and is the sensible place to start with trimming things down.
>
> Optimising to just pyc files is an optimisation further than most
> people find they need and will be much harder to do.
>
> Cheers,
>
> Richard
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
Yann Dirson <yann@blade-group.com>
Blade / Shadow -- http://shadow.tech
next prev parent reply other threads:[~2019-10-19 15:21 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
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 [this message]
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='CA+4=imYxNpiox1pPwi52LeL56vT+ZSpFgj9EStYh+EXmirBNeA@mail.gmail.com' \
--to=yann.dirson@blade-group.com \
--cc=richard.purdie@linuxfoundation.org \
--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.