[oe] Building Python extensions

Dr. Michael Lauer mickey at vanille-media.de
Wed Aug 22 13:23:13 UTC 2007


(Sorry for the long delay... :)

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).

> 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?

> 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.

Regards,

:M:
-- 
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de





More information about the Openembedded-devel mailing list