Re: [Hamlib-developer] python binding autoconfiscation

[Stephane F. <f8...@fr...>]

On Sun, Apr 04, 2010, Nate Bargmann wrote:
[..]
> As for Python slowing the build, I've not seen it as I disable the Perl
> and Python bindings on my local builds.  Is there any benefit to having
> them built by default?  Would it be "better" to disable them by default
> so that people "who know what they are doing" could enable them if
> needed?

I agree with you, they should be disabled by default.


Mon, Apr 05, 2010, Thomas Beierlein skribis:
> On some machines the search for the path to the python library takes very long
> (1..3 minutes). That comes from the very old python.m4 macro we use at the
> moment. If the python lib libpython.so... can not be found in the old standard
> locations it tries to find it via some 'find' commands. That can take a long
> time if you have a lot of files in /usr.
> 
> The funny point is that we do not need that library it looks for at all.

But we do need PYTHON_CPPFLAGS. Some systems may need the library, and/or
its dependencies, but we can leave that.

> Maybe we should adapt to the newer ax_python.m4 macro from the autoconf 
> archive. But we would have to adapt configure.ac accordingly.

Good idea. Anyway, we'll have to adapt configure.ac in order to follow
Nate's suggestion.

73
-- 
Stephane - F8CFE