Age | Commit message (Collapse) | Author | Files |
|
Converted most of python site-packages references to PYTHON_SITEPACKAGES_DIR.
Signed-off-by: Roman I Khimov <khimov@altell.ru>
|
|
Allows to inherit that in packages containing Python extensions but still tightly
control packaging of those extensions. Mainly for the cases where you want
those python modules/extensions/parts to be packaged separately from the main
package in order not to introduce python dependency where you don't need it.
Technically, you can do it with distutils-common-base, but it might require
more FILES_* work than with python-dir.
Introduce PYTHON_SITEPACKAGES_DIR along the way, site-packages directory is
referenced frequently enough within class files, but some recipes also pack this
directory as
${libdir}/python2.5/site-packages
${libdir}/python2.6/site-packages
${libdir}/python*/site-packages
/usr/lib/python*/site-packages
${libdir}/*/site-packages
all of which are not perfect.
Signed-off-by: Roman I Khimov <khimov@altell.ru>
|
|
* use += instead of =
this appends new file paths to include instead of replacing the
current definition
Signed-off-by: Rolf Leggewie <oe-devel@rolf.leggewie.biz>
Acked-by: Graeme Gregory <dp@xora.org.uk>
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Michael 'Mickey' Lauer <mickey@vanille-media.de>
|
|
python-native isn't in DEPENDS.
Signed-off-by: Chris Larson <clarson@mvista.com>
Acked-by: Michael 'Mickey' Lauer <mlauer@vanille-media.de>
|
|
support datadir/pkgconfig...
* http://lists.linuxtogo.org/pipermail/openembedded-devel/2009-April/009963.html
|
|
distutils-common-base.bbclass
Create a new class distutils-common-base.bbclass which holds the common
parts that can be used in native and target packages which need to use
distutils funtionality.
rpm, libxml2, zope are currently using them and needed to use
distutils-native-base for native recipes.
rpm and libxml need to defer the processing of certain configure
parameters which we evaluate using python. So we need to have python-native
built before we can process them. Hence we can not use EXTRA_OECONF
which is a python variable and gets expanded during parsing recipes
and ofcourse we have not yet built python-native.
We pass these extra options as a separate shell variable to do_configure
which we evaluate when that task is executing.
|