From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building python without downloading dependencies for all modules
Date: Sun, 19 Apr 2009 20:44:37 +0200 [thread overview]
Message-ID: <200904192044.39103.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <c15f914f0904180744m137b82c5r552a3b8431954165@mail.gmail.com>
Dnia sobota, 18 kwietnia 2009 o 16:44:29 Bart Staal napisał(a):
> I'm a relative new guy to the OE world, but I fairly managed to find
> my way through it and build images for my NAS (ch3snas).
If it is not in OE then will you merge support for it?
> I want to equip my NAS with the python interpreter. If I 'bitbake
> python' a big nasty list of dependencies is pulled from the net, eg
> x11 headers, sqlite, openssl, tcltk, etc, etc. Calling 'bitbake
> python-core' doesn't work, but I now I understand that this package
> is created if the python recipe is built.
> I'd like to have a way to only download/build the core python stuff,
> with only a few modules which I really need. Is there a way to
> achieve this with the existing python recipes in the OE repository or
> should I create my own python recipes?
We build Python with lot of extensions. Each module is packaged
separately so you can choose which exactly parts you need. What you see
is build dependencies (which are huge) but result will require all those
extra libs only if you will install all modules.
So live with it or change DEPENDS line in python_VER.bb recipe (but that
way is not so supported by us).
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
prev parent reply other threads:[~2009-04-19 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 14:44 Building python without downloading dependencies for all modules Bart Staal
2009-04-19 18:44 ` Marcin Juszkiewicz [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=200904192044.39103.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox