I submitted my patches to automake to Tom Tromey last year. Apparently
there was another set of patches for python support that someone else
submitted.
I hadn't checked up on whether he had actually commited the patches for a
while. What he has added looks like a combination of my patches and
Andrew Dalke's ones. It looks like Andrew's configure macros and my
patches for the actual automake program.
The patches are set up for installing the package relative to the prefix
passed to configure rather than relative to python's installation. This
is closer to what you would expect of a program with a configure script,
but may lead to a non working install, which is not optimal.
I should probably switch over to the official python support in automake,
and check that it all works correctly.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Sat, 11 Mar 2000 [EMAIL PROTECTED] wrote:
>
> What is the current status of Python support in Automake?
>
> I have the current CVS version of automake that includes some support
> for python and it seem to be different than the pyautomake used by
> pygtk.
>
> I'm trying to create a c extension with a configure script similar to
> pygtk. Is this currently possible using the 'official' python support in
> Automake? I'm having trouble creating a module named foomodule.so.
> The shared library support in Automake wants a name like libfoomodule.so.
>
> Lee Taylor
> Lawrence Livermore National Laboratory
>
>
>
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
