Quoting Ralf Wildenhues [EMAIL PROTECTED]:
Hello Benoit,
* Benoit Sigoure wrote on Sun, Jun 17, 2007 at 01:16:35AM CEST:
I've reviewed the patches I proposed back in March, completed them with
tests, ChangeLog and NEWS entries. If they are accepted, I'll write the
documentation.
Please
Ralf Wildenhues wrote:
Does this help?
http://www.gnu.org/software/autoconf/manual/html_node/Defining-Directories.html
Cheers,
Ralf
Yeah! That helped alot.
Thanks,
Jeshua
--
View this message in context:
I notice that automake is currently generating Makefiles that violate
the gnu coding conventions. Specifically, it's generating rules for
rebuilding Makefile from Makefile.in and Makefile.in from
Makefile.am which requires automake. And yet the gnu coding standards
specify:
The
On Mon, 2007-06-18 at 17:27 -0700, K. Richard Pixley wrote:
My question today is... is there any hope of bringing automake
generated
Makefiles back into line with the GNU coding standards so that these
applications will work once again?
Use AM_MAINTAINER_MODE in your package; this will
Bob Proulx wrote:
K. Richard Pixley wrote:
I notice that automake is currently generating Makefiles that violate
the gnu coding conventions.
Hmm... I don't think that automake violates the standards. In the
normal case it is not required to have automake installed. Someone
who is
K. Richard Pixley wrote:
even be interested in regenerationg Makefile.in's automagically. As is,
typical builders, (ie, not maintainers), are required to install
automake in order to build packages requiring automake.
I think you're generalizing this to a degree that's not the case.
Most
On Mon, 18 Jun 2007, K. Richard Pixley wrote:
Bob Proulx wrote:
Are we talking about one of your own projects? Or are we talking
about other projects that you are trying to build?
Projects that I'm trying to build. Hundreds of them. Projects that won't be
fixed in their current