Re: Automake with Python scripts

[Stepan Kasal]

Hello,

On Sun, Jul 30, 2006 at 02:24:52AM +0530, Debarshi 'Rishi' Ray wrote:
> With this set-up 'make install' throws:
> make[2]: *** No rule to make target `xmlrpclibauth.py', needed by
> `install-pyexecPYTHON'.  Stop.
> make[2]: Leaving directory `/devel/GNOWSYS/g7/gnow/src'

I really cannot understand how make can print this error if the file
`xmlrpclibauth.py' is present in /devel/GNOWSYS/g7/gnow/src

BTW, which version of Automake are you using?  1.9.6 is the latest
one.

More comments:

> bin_SCRIPTS = gnow

if this is a python script, you should perhaps use
bin_PYTHON = gnow

If you want to make compiled version of the script, Automake needs
the filename with extension *.py.  If that it a problem, you can
create a wrapper or a symlink.

If you want to use the SCRIPTS primary, dist_bin_SCRIPTS would be
better.

> configure.ac>>>>>
> AM_INIT_AUTOMAKE([-Wall])

This line should go just after AC_INIT, at least before any other
AM_* macro calls.

> AC_CHECK_PROG([found],[python],[yes],[no])

Why do you need this?  Try deleting it.

> AC_OUTPUT([Makefile doc/Makefile src/Makefile])

This is an absolete form, use:

AC_CONFIG_FILES([Makefile doc/Makefile src/Makefile])
AC_OUTPUT

> Makefile.am>>>>
> 
> EXTRA_DIST = AUTHORS ChangeLog COPYING INSTALL NEWS README

This is not necessary, these files are distributed automatically.

> MAINTAINERCLEANFILES = Makefile.in configure
> 
> src/Makefile.am>>>>
> 
> MAINTAINERCLEANFILES = Makefile.in

The standard target `maintainer-clean' should leave the tree in a
state where `configure&&make' is still possible.
If you need a return-to-clean-cvs-checkout type target, you should
rather use another name.

> Using 'pyexecdir_PYTHON' in src/Makefile.am leads to an error while

Indeed, `foo_PRIMARY' is coupled with `foodir', and `pyexecdir' is
defined by AM_PATH_PYTHON, while `pyexecdirdir' is a nonsense.

HTH,
        Stepan Kasal