Robert Collins wrote:
Now, for the problem reported the root problem here is *NOT*
autotools brokenness. It's CVS being broken (unless I'm seriously
mistaken).
I did forget to thanks you all..
Finally I know much more about how to use the autotools and what is
actually done by each tool.
BTW, as serendipity (or synchronicity) would have it, those who read DDJ
might have noticed the article about Cmake (http://www.cmake.org/) that
appeared in the latest issue. Cmake looks like it might be worth looking
into (and yes it is Open Source software).
Soren A
--
Yes, it's really
At 08:40 PM 12/4/2002, Soren A wrote:
BTW, as serendipity (or synchronicity) would have it, those who read DDJ
might have noticed the article about Cmake (http://www.cmake.org/) that
appeared in the latest issue. Cmake looks like it might be worth looking
into (and yes it is Open Source
On Mon, 2002-12-02 at 11:36, Soren A wrote:
At the very LEAST, something that does what AM_MAINTAINER_MODE causes,
should have been the *default* for all autotool'd packages, and only by
significant contortions should it have been made possible to cause all that
default behavior to get
Robert Collins [EMAIL PROTECTED] wrote in
1038820917.2953.13.camel@lifelesswks:">news:1038820917.2953.13.camel@lifelesswks:
On Mon, 2002-12-02 at 11:36, Soren A wrote:
At the very LEAST, something that does what AM_MAINTAINER_MODE
causes, should have been the *default* for all autotool'd
Doing aclocal automake autoconf as the autobook suggests
doesn't change things... =(
(or: it does seldom work, but usually doesn't.. that's why I'm
thinking about granularity in NT's timekeeping)
automake 1.7.x and later require autoconf-2.54 or newer. Ordinarily,
the wrapper scripts in
Lapo Luchini wrote:
That's not the point: I have no problem on my cybwin developement
machine: the problem is that ./configure-generated Makefile tries to
call the autotools on each different machine, even in no-one changed
configure.in or Makefile.am
The client machine shouldn't need
Lapo got me started. Blame him ;-)...
Charles Wilson [EMAIL PROTECTED] wrote in
[EMAIL PROTECTED]:">news:[EMAIL PROTECTED]:
The client machine shouldn't need autotools or the know-how to use
them, right?
Not necessarily. If configure.in doesn't have AM_MAINTAINER_MODE,
then the default
Hi!
Finally I decided to study seriously the autotools (thanks for the
references, Nicholas!).. but I have a small problem:
(cyberone is my CygWin/WinXP desktop machine, cyberx is my FreeBSD
home-server machine)
cyberone$ autoreconf
cyberone$ rsync -vrLe ssh --delete * lapo@cyberx:project/
Lapo Luchini [EMAIL PROTECTED] wrote:
Hi!
Finally I decided to study seriously the autotools (thanks for the
references, Nicholas!).. but I have a small problem:
(cyberone is my CygWin/WinXP desktop machine, cyberx is my FreeBSD
home-server machine)
cyberone$ autoreconf
cyberone$ rsync
I believe that autoreconf isn't entirely reliable.
This is the reason that projects (e.g. libgetopt++) often have a
bootstrap.sh which runs the relevant autotools.
Doing aclocal automake autoconf as the autobook suggests doesn't
change things... =(
(or: it does seldom work, but usually
Lapo Luchini wrote:
I believe that autoreconf isn't entirely reliable.
This is the reason that projects (e.g. libgetopt++) often have a
bootstrap.sh which runs the relevant autotools.
Doing aclocal automake autoconf as the autobook suggests doesn't
change things... =(
(or: it does
12 matches
Mail list logo
