Hi Carsten, Am 13.02.2014 um 10:18 schrieb Carsten Grzemba <[email protected]>:
> 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 This doesn’t matter at all, just make sure to always use either the dotted or the underline notation. I guess Peter was not aware that dots are allowed in the category file, feel free to adjust (and test!) it. Best regards — Dago > > Carsten > > Am 12.02.14 schrieb Maciej (Matchek) Bliziński <[email protected]>: >> >> 2014-02-12 11:43 GMT+00:00 Carsten Grzemba <[email protected]>: >> 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 -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
smime.p7s
Description: S/MIME cryptographic signature
