All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Including python libs
Date: Fri, 30 Dec 2011 16:39:35 +0100	[thread overview]
Message-ID: <20111230153935.GI16885@jama.jama.net> (raw)
In-Reply-To: <012301ccc707$664a36e0$32dea4a0$@gmail.com>

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

On Fri, Dec 30, 2011 at 08:26:25AM -0700, itodroid wrote:
> Greetings all!
> 
> I'm having a little trouble figuring out the "right" way to include some
> extra python libraries into a recipe, and for the life of me, I cannot
> figure it out.  I'm using Python2.6 and I have a few python scripts that
> depend on httplib.  I've found that httplib.py is contained within
> "python-2.6.6-ml12.2".  
> 
> In my recipe, I've tried "include python-2.6.6ml12.2" and also "DEPEND +=
> python-2.6.6ml12.2", neither of which actually include the
> /usr/lib/python2.6/<python libs> into my rootfs.
> 
> I believe that httplib is part of python-netclient which appears to be
> provided by python-2.6-manifest.inc.  I've also tried including this
> manifest file into my recipe, but still, I cannot get the libraries into my
> rootfs.
> 
> Can anyone provide some insight as to what I'm doing wrong?  Thanks in
> advance.

If it's part of python itself then
RDEPENDS_${PN} += "python"
if it's in python-netclient then
RDEPENDS_${PN} += "python-netclient"

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2011-12-30 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 15:26 Including python libs itodroid
2011-12-30 15:39 ` Martin Jansa [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=20111230153935.GI16885@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --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 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.