My kneejerk reaction is that Python would be a good language
for Autoconf to deal with. The hard part would probably
be writing the documentation -- is that something you
could do? The idea would be to come up with a patch
to the Autoconf sources.
Yes, that's no problem. I may have to put
things like AC_LANG_PROG to call arbitrary
Python code.
Since this task of implementing configure scripts for Python packages
was considered to be of rather high importance by rms et al., I'm
wondering how best to submit these macros. There are other Python macros
in the Autoconf Macro Archive
My kneejerk reaction is that Python would be a good language
for Autoconf to deal with. The hard part would probably
be writing the documentation -- is that something you
could do? The idea would be to come up with a patch
to the Autoconf sources.
___
On 09/23/2012 08:31 PM, Brandon Invergo wrote:
[SNIP]
python.m4 in Automake is much more complete, and these macros are the
direct decendents of that file, but to me at least, it's confusing that
these macros should be implemented in Automake and not in Autoconf (or
Autoconf Archive for
Here's one I did for a project where I want to use 2.0. Since
python is still 1.5.2 on Debian, it had to be smart enough to see
that python's not 2.0...
It's not perfect... but it Works For Me(tm) ;-)
AC_DEFUN(jae_PYTHON,
[
# Try to find Python in the path
AC_PATH_PROG(PATH_TO_PYTHON, python)
