Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Jate S <jatedev@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
	Jens Lucius <jenslucius@freenet.de>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [yocto] python tkinter dependencies
Date: Fri, 11 Jul 2014 00:30:30 +0200	[thread overview]
Message-ID: <20140710223030.GD2433@jama> (raw)
In-Reply-To: <CAPphmgaa8uhXjwDq+c-GUgyyqhcPB-gdsHmAxq4_c_x1acBooQ@mail.gmail.com>

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

On Thu, Jul 10, 2014 at 04:11:29PM -0400, Jate S wrote:
> - Python-tkinter requires the tk recipe in meta-oe, so you must add
> this layer for your build.
> - I am on dora. I found that I needed commit "tk: make multilib build
> compatible and fix library install" made on 12/5/2013
> (1ca29d1cda0d007c4e6a28fe1a4037b4029ad7ae).
> - I created a bbappend for python. In this I added
> DEPENDS_class-target on tk, and RDEPENDS_class-target on tk and
> tk-lib. Also, I did a SRC_URI replace to eliminate the
> avoid_warning_about_tkinter.patch file.
> 
> I was able to build and use python-tkinter successfully.
> 
> The question now is if this should go into meta-oe or oe-core. And how.
> 
> The tcl recipe is in oe-core, but not tk. I'm not yet sure why this
> is. Does anybody know?

You can use PACKAGECONFIG for optional dependencies like tk, that way
patch adding PACKAGECONFIG can go to oe-core and only people with
meta-oe and tk available will enable it.

> 
> - Jate S.
> 
> On Wed, Jul 2, 2014 at 1:51 AM, Jens Lucius <jenslucius@freenet.de> wrote:
> > Hi
> >
> > It worked for me in my build env after trying several things.
> >
> > I did setup a new yocto some while ago and actually had the same problems
> > again.
> >
> > There is a patch in python about tkinter (03-fix-tkinter-detection.patch).
> >
> > I removed that, did a fresh rebuild of python (-c clean) and did a rebuild
> > of my image (as no new image was written by building my image after
> > rebuilding python).
> >
> > Either of these did work for me, maybe somebody knows exactly which step :-)
> >
> > Jens
> >
> > Am 02.07.2014 05:41, schrieb Jate S:
> >
> >> The python-tkinter module requires _tkinter. A result from a websearch
> >> suggested that I needed to make sure tk (from meta-oe/meta-oe) and tcl
> >> were installed before compiling python.
> >>
> >> I added a DEPENDS on the tk and tcl recipes to both python and
> >> python-tkinter in a python_2.7.3.bbappend. It did not work and was
> >> never built.
> >>
> >> I'm looking for tips to figure out what is going on. Thanks.
> >>
> >>
> >> - Jate S.
> >
> >
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

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

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

  reply	other threads:[~2014-07-10 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPphmgZ+ivQYXuYHLWfzQF9QySVnd=YtbM=fEjfA_7hp3iFq1A@mail.gmail.com>
     [not found] ` <53B39DCE.9060705@freenet.de>
2014-07-10 20:11   ` python tkinter dependencies Jate S
2014-07-10 22:30     ` Martin Jansa [this message]
2014-07-14 10:38     ` [yocto] " Paul Eggleton

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=20140710223030.GD2433@jama \
    --to=martin.jansa@gmail.com \
    --cc=jatedev@gmail.com \
    --cc=jenslucius@freenet.de \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox