On 22.3.2018 14:48, Bob Friesenhahn wrote:
On Thu, 22 Mar 2018, Matěj Týč wrote:
On 21.3.2018 22:34, Bob Friesenhahn wrote:
...
Majority of packages that use Autotools are C/C++ libraries, and they
may want to build bindings for Python. As Python2 is the only
supported Python e.g. in
On 21.3.2018 22:34, Bob Friesenhahn wrote:
On Wed, 21 Mar 2018, Matěj Týč wrote:
The question stands like this: Is there a demand on automake side to
fix this issue - to allow developers addressing multiple Python
interpreters of different major versions? If so, I think that I can
come up
Hello,
there is a Python autoconf support macro in automake AM_PATH_PYTHON that
can be used to find Python interpreters.
The problem of this macro is that it treats Python versions in a linear
manner - if I write that I want Python >= 2.7 on a machine that has
Python 2.6 and Python 3.1, I pr
On 29 April 2010 00:04, Bruce Korb wrote:
> Hi Matěj,
>
> On Wed, Apr 28, 2010 at 1:48 PM, Matěj Týč wrote:
>> I am quite sure that one .tpl and .def tuple can result in multiple
>> files, all of them having the same basename, but possibly different
>> extensions.
&g
-- Forwarded message --
From: Matěj Týč
Date: 28 April 2010 22:48
Subject: Re: GNU autogen code generation
To: autoconf
On Wed, 2010-04-28 at 08:01 +0200, Ralf Wildenhues wrote:
> Hello Matěj,
>
> * NightStrike wrote on Wed, Apr 28, 2010 at 12:49:56AM CEST:
> >
Hello,
I use GNU Autogen to generate files to my project.
A little introduction:
Autogen uses two files: A definition file, let's say foo.def and a
template file, may be foo-template.tpl
If I pass the definition file to autogen, it should use the information
in it to find the template file and to
On Tue, 2009-02-24 at 09:20 +0100, Ralf Wildenhues wrote:
> Hello Matěj,
>
> * Matěj Týč wrote on Mon, Feb 23, 2009 at 04:01:34PM CET:
> > The problem is that running 'make distcheck' results in error since
> > the EPS images that should be there aren't the
Hello,
I use automake in one of my project along with texinfo.
That project has documentation full of images. As you probably know,
'make pdf' makes a PDF document from JPGs and PNGs, whereas 'make dvi'
requires EPSs. However, EPS images are insanely large (in this case
like 15 times larger than JP
What I do (not sure whether it is correct) is that I define a variable
in configure.ac:
AC_ARG_WITH([datadir],
[AS_HELP_STRING([--with-datadir=path-to-your-foo-datafiles],
[Normally you don't have to use this, but it is
handy when you
want to use foo withou
> Sorry about the inconvenience. git master contains AM_COND_IF only...
I understand, thank you for clarification! It is quite funny how many
google results can one get on a macro that is not accessible to most
people. It even seems that some people are already using it :-)
> Grepping in the automake tree reveals m4/cond-if.m4. The file should
> have been installed into /usr/share/aclocal-1.10.2 (+/- prefix).
Thank you for pointing out! I have just /usr/share/aclocal-1.10
directory, although aclocal claims that it is aclocal (GNU automake)
1.10.2
The AM_COND_IF macro
> Did you try regenerating the aclocal files?- usually done by `autoreconf -fi`.
Yes, I tried it and it did not help, I still get the error. Are there
any files where the macro is supposed to be defined to check?
> I could not find it in the manual either, so the macro is probably
> not the right one to start with.
It is in the manual, of course (that's where I have found it). Look
here:
http://sources.redhat.com/automake/automake.html#Conditionals
> I could not find it in the manual either, so the macro is probably
> not the right one to start with.
It is in the manual, of course (that's where I have found it). Look
here:
http://sources.redhat.com/automake/automake.html#Conditionals
Hello,
I would like to use the AM_COND_IF macro in my configure.ac, but when I
run autoreconf, I get an error message saying that the macro couldn't be
found anywhere.
I have tried to google it, but it seems that nobody has this problem...
Any suggestions?
The error message I get:
configure.ac:2
There is a nice up-to-date series on autotools here,
http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool
I have found it really helpful. But maybe autotools are an overkill if
you have such special program with just one source file. When you are
finished, just p
Hello, Ralf,
here are things you have requested, if the previous mails wasn't
satisfactory ;-)
> First, do you build in-tree (./configure ...) or out-of-tree
>
(../path/to/configure ...)?
I build in-tree...
Second, if you
> find $top_srcdir $top_builddir -name \*.info | xargs rm -f
>
find $t
> First, do you build in-tree (./configure ...) or out-of-tree
> (../path/to/configure ...)?
I usually build in-tree and make distcheck build out-of-tree. Never came
across an .info file, though (I have used find -name "*.info" as told
below)
> Second, if you
> find $top_srcdir $top_builddir -na
> Please just post all of the output, it is often much easier for me to
> see then what went wrong.
OK, you have asked for it :-) I send output of 'make distcheck' and
'automake --verbose' zipped in the attachment
Unfortunately, it is not a simple foo project...
> The info file should have been bu
Thank you very much for your quick reply,
>
> Please post the output of 'make distcheck', and state which automake
> version you're using. Thanks.
I use automake (GNU automake) 1.10.1
make distcheck just complains that it can't find the foo.info file so it
can't install it (or at least it seems
Hello,
I use Texinfo to document my project and I have a foo.texi file in doc/
subdirectory.
I have these lines in the doc/Makefile.am:
info_TEXINFOS = foo.texi
EXTRA_DIST = images/foo1.png etc.
I also have the doc/ directory and makefile "registered" in root
Makefile.am and in configure.ac
ma
Hello Michel,
...
>
Adding to that the check could be implemented in many different ways :
> an autoconf macro, calling a script (sdl-config for example), using
> pkgconfig...
Stick with AC_CHECK_LIBS, see reasons below.
>
> Side question : a good distro could enforce that each library will
> pr
Thank you for your reply, Braden,
> > I am particulary searching for a manner how to specify the library
> > name
> > in a smart way since libtool can be very creative when decorating the
> > library name (if you use the -version-number etc. options).
>
> You don't use that information when lin
Thank you for your reply, Dan
> And where is the problem? E.g.
>
> Name: @PACKAGE@
>
This does not work. I need a name of the library that libtool produces
in the end...
> and then process the .pc.in by configure (AC_CONFIG_FILES). If you don't want
> to
> use $PACKAGE, well then use some self
Hello friends,
I would like to inquire whether there is someone here that generates .pc
files in his autotools-powered project (presumably a project containing
libraries).
I am particulary searching for a manner how to specify the library name
in a smart way since libtool can be very creative when
25 matches
Mail list logo
