On Tue, Mar 3, 2009 at 1:32 PM, Ralf Wildenhues wrote:
> * Allan Caffee wrote on Tue, Mar 03, 2009 at 07:14:51PM CET:
>> I just wanted to follow up on this. I decided not to post the
>> series to the list.
>
> Why not? If it is larger than a couple dozen KB, then you can still use
> the -patches
* Allan Caffee wrote on Tue, Mar 03, 2009 at 07:14:51PM CET:
> On Fri, Feb 13, 2009 at 10:43 AM, Allan Caffee wrote:
> > Ideally the macro archive would provide a way to
> > produce these rules in a way that they would be available for Automake to
> > work
> > its magic. I'm working on a patch s
On Fri, Feb 13, 2009 at 10:43 AM, Allan Caffee wrote:
> Ideally the macro archive would provide a way to
> produce these rules in a way that they would be available for Automake to work
> its magic. I'm working on a patch series that would allow macro developers
> provide an Automake include-able
On Thu, 12 Feb 2009, Ralf Wildenhues wrote:
> > I've noticed that a handful of the packages in the Autoconf archives
> > use the macros AX_ADD_AM_MACRO and AX_ADD_RECURSIVE_AM_MACRO. These
> > macros add targets and variable assignments to a generated file
> > $(top_srcdir)/aminclude.am. Users ar
Hello Allan,
* Allan Caffee wrote on Wed, Feb 04, 2009 at 12:38:01AM CET:
> First of all I wasn't really sure where to start this thread so if
> this isn't the appropriate place I apologize.
This is very well appropriate here.
> I've noticed that a handful of the packages in the Autoconf archive
First of all I wasn't really sure where to start this thread so if this isn't
the appropriate place I apologize.
I've noticed that a handful of the packages in the Autoconf archives use the
macros AX_ADD_AM_MACRO and AX_ADD_RECURSIVE_AM_MACRO. These macros add targets
and variable assignments to
