[CF-Devel] Madhatter? (Python plugin automake)

[Todd Mitchell]

Mark said:
>
     
        So where are the Python.h files for the two versions, as well as where
     
     are the
>
     
      libraries located?
     
     >
     
     
     >
     
        The Makfiles are automatically generated, so changing the Makefile
     
     probably
>
     
      isn't the right long term solution - instead, the detection logic needs to
     
     be
>
     
      modified to do the right thing.
     
     

The autobuild does use the proper Python.h (on my system I have
/usr/include/python1.5 and /usr/include/python2.1 - and the CPPFLAGS that is
generated in the Makefile is -I/usr/include/python2.1

(note on another system I have python2.2 instead and it is happy using that
as well- generating -I/usr/include/python2.2,  so this could be considered
interchangable between the 2x versions)

The problem is with the python libraries.  The Makefile when generated, gets
this inserted for @PYTHON_LIB@ :
/usr/lib/python1.5/config/libpython1.5a
/usr/lib/python2.1/config/libpython2.1a

In the plugin directory the Makefile.in says PYTHON_LIB =@PYTHON_LIB@

As I mentioned since the plugin was generated against Python2.1 headers
(properly), I had to remove the portions of the PYTHON_LIB pointing to
libpython1.5a or most of the code would bomb.

Not sure how it works - but I imagine this problem would be found on older
redhat type systems (prior to 7.3) and others which rely on having the
python1.5 libraries.