From: Martin Jansa <martin.jansa@gmail.com>
To: Jate S <jatedev@gmail.com>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python2: Add PACKAGECONFIG for tkinter to support tk from meta-oe
Date: Mon, 21 Jul 2014 05:08:03 +0200 [thread overview]
Message-ID: <20140721030803.GI22875@jama> (raw)
In-Reply-To: <CAPphmgZhVbj-Fb+XOL3p4bUVa_T0=AZnYuxetWPYqV5ZeUjNww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
On Sun, Jul 20, 2014 at 09:01:05PM -0400, Jate S wrote:
> The presence of the tk library determines whether python's compile
> task will build tkinter. Then the presence of python-tkinter in
> IMAGE_INSTALL will then determine whether it is installed.
>
> In the absence of tk provided by meta-oe, the python recipe will
> install an empty python-tkinter package.
>
> I cannot think of a cleaner way to do this right now. Ideally the
> package python-tkinter could trigger a python DEPENDS on tk...
>
>
> Martin, you originally suggested the PACKAGECONFIG. Do you have any
> further thoughts on this?
Richard just submitted patch to explicitly disable tk, extend the patch
to make it configurable and use this new option from PACKAGECONFIG
http://git.openembedded.org/openembedded-core/commit/?id=53ae544cfdac22c82af452b8c7ebe6664296bd9b
>
> - Jate S.
>
>
> On Mon, Jul 14, 2014 at 2:32 PM, Enrico Scholz
> <enrico.scholz@sigma-chemnitz.de> wrote:
> > Jate S <jatedev@gmail.com> writes:
> >
> >> Python 2.7.x does not use an explicit configure option for tk support.
> >> Instead, it tries to detect the tk and tcl libraries before compiling
> >> python-tkinter.
> >
> > Your patch does not solve the issue of non-deterministic builds. When
> > tk was added by some other way, python will get tkinter support although
> > PACKAGECONFIG was not set.
> >
> > An idea to make build deterministic might be patching of detect_modules()
> > in setup.py to add disabled modules to 'missing'. E.g.
> >
> > | missing.append('_tkinter')
> > |
> > |+ missing.extend(os.environ('OE_HACK_MISSING').split())
> > | return missing
> >
> > Probably there are better/cleaner ways but I am not familar with python
> > distutils.
> >
> >
> > Enrico
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-07-21 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 14:46 [PATCH] python2: Add PACKAGECONFIG for tkinter to support tk from meta-oe Jate Sujjavanich
2014-07-14 15:31 ` Enrico Scholz
2014-07-14 17:58 ` Jate S
2014-07-14 18:32 ` Enrico Scholz
2014-07-21 1:01 ` Jate S
2014-07-21 3:08 ` 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=20140721030803.GI22875@jama \
--to=martin.jansa@gmail.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=jatedev@gmail.com \
--cc=openembedded-core@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