How to build python2.7 packages

[Carsten Grzemba]

Finally I have stolen the magic from http://sourceforge.net/p/gar/code/HEAD/tree/csw/mgar/pkg/file/trunk/Makefile, 
but for the configuration step was this this hint in configure.ac important:

# The version of python used is determined by the executable pointed to by
# the PYTHON environment variable. For instance if your system installs
# Python 3 as python3 to configure to compile pygobject under Python 3
# you would do this:
# $> PYTHON=python3 ./configure

So I have to add in recipe also:

EXTRA_CONFIGURE_ENV = PYTHON=python$(PYTHON_VERSION)

In .buildsys/v2/categories/python/categor.mk I have seen that the underline natation is used:

MODULATIONS_PYTHON_VERSION ?= 2_6 2_7

Is this correct? I have to use the dotted notation for work:
MODULATIONS_PYTHON_VERSION = 2.6 2.7

Carsten

 Am 12.02.14 schrieb Maciej (Matchek) Bliziński  <maciej at opencsw.org>:
> 2014-02-12 11:43 GMT+00:00 Carsten Grzemba <grzemba at contac-dt.de>:
>  
> > What is the correct way to package for both (or all) versions of python? 
> > I can not use the category python for pygtk and pygobject
> >  
> 
> 
> You can't/shouldn't put category modulators in the recipe.
> 
> 
> I was thinking that maybe you can have a separate build recipe just for the Python modules? It would be a separate Makefile, building from the same sources, but only generating the Python modules. I don't know if it's a workable idea, but maybe it's worth investigating?
>  
> 
> Maciej
> 
> 
> 
>  
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140213/816bbe7b/attachment.html>