Currently, my automake alterations install the scripts using the value of
the INSTALL_DATA make variable. If you think that python scripts should
be installed with executable permissions, edit python.am, and replace
occurences of INSTALL_DATA with INSTALL_PROGRAM.
On the other hand, an executable script is really a script, and won't
benefit from byte compilation, so using the bin_SCRIPT primary may be a
better choice.
James Henstridge.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Wed, 13 Jan 1999, Philip Dawes wrote:
> I've got a python program that I'm using autoconf/automake with. Problem is
> that when it gets installed (in ${exec_prefix}/bin) it doesn't have
> executable permissions set. Is there anyway of doing this cleanly with the
> python extensions to automake?
>
> At the moment I'm using:
>
> foo_dir = $(exec_prefix)/bin
> foo_PYTHON = foo.py
>
> Cheers,
>
> Phil.
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
