Re: Building Python extensions

[Marcin Juszkiewicz <openembedded@hrw.one.pl>]

Dnia środa, 22 sierpnia 2007, Dr. Michael Lauer napisał:
> Marcin Juszkiewicz wrote on 23th of March:
> > When we build Python extension (for example python-pygtk2) configure
> > script builds one test program to check does it has Python headers.

> So this is a problem with python packages using autotools only, right?
> (I remember I patched distutils to take care about that).

looks like it

> > I got fix for it of course. M4 scripts of each used Python extensions
> > use macro AM_CHECK_PYTHON_HEADERS which I edited to add one option to
> > configure: --with-python-includes which should be pointed to
> > ${STAGING_INCDIR}/../ to get it working.
>
> So just adding to EXTRA_OECONF will do?

Need to patch acinclude.m4 too.

> > I will sync some of Python extensions with this fix from Poky into
> > OpenEmbedded in next days (python-pygtk2 already pushed).
>
> Since we don't have that many extensions using autotools, we can fix
> this easily.

you or me?

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

        Linux! -- Because a big world can not fit in small windows.