On Wed, Mar 4, 2009 at 10:39 PM, Allan Caffee wrote:
> The patch series that follows is intended to improve (hopefully replace) the
> existing macro AX_ADD_AM_MACRO. The purpose being to address the fact that
> this macro does _not_ create rules for Automake but rather writes a f
These changes have not been tested very well since I don't have the software
setup to use either one. It's also worth mentioning that AX_DIST_MSI appears
to use GNU Make syntax which will cause Automake to complain unless portability
warnings are disabled.
Please feel free to modify this patch an
The macros AX_UPLOAD, AX_INSTALL_FILES, and AX_EXTRA_DIST which are often used
in conjunction with AX_DIST_RPM were also updated to use
AX_ADD_AM_MACRO_STATIC.
Thanks go to Ralf Wildenhues for the idea of adding local cleanup and
distribution targets as prerequisites the *-local/*-hook targets.
--
data to the specified Autoconf is run. If you want
+# to append to a file when configure is run use AX_APPEND_TO_FILE instead.
+#
+# LAST MODIFICATION
+#
+# 2009-02-03
+#
+# COPYLEFT
+#
+# Copyright (c) 2009 Allan Caffee
+#
+# Copying and distribution of this file, with or without modific
The patch series that follows is intended to improve (hopefully replace) the
existing macro AX_ADD_AM_MACRO. The purpose being to address the fact that
this macro does _not_ create rules for Automake but rather writes a file to be
included by Make itself. The first patch in the series includes th
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 yo
On Tue, Mar 3, 2009 at 5:46 PM, Ralf Wildenhues wrote:
> For cleanup, you can add a convention that no snippet overwrite the
> documented -local/-hook targets, but only add prerequisites to them.
> That won't help you in all cases, but most of them.
>
> distclean-local: distclean-local-doxygen
>
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
On Sat, 28 Feb 2009, Ralf Wildenhues wrote:
> * Allan Caffee wrote on Thu, Feb 26, 2009 at 02:49:16PM CET:
> > That is certainly one possibility. Unfortunately though that means that
> > in the Makefile.am files you _must_ use += since Automake will error out
> > if you assig
On Thu, 26 Feb 2009, Jeroen N. Witmond [Bahco] wrote:
> I'm not an expert on automake, but perhaps you've chosen the wrong
> solution to your problem: maintainer-cleaning some additional files. I
> would have thought target maintainer-clean-local was invented for this
> purpose! :) (However, I have
Thank you both for your speedy responses.
On Wed, Feb 25, 2009 at 7:04 PM, Jan Engelhardt wrote:
> In one project I use -- though not a "header + main makefile" but
> a "main makefile + subordinates" layout --:
>
> # Makefile.am (http://tinyurl.com/dhxfwf)
> bin_PROGRAMS =
> include bar/Automakef
On Wed, 25 Feb 2009, Ralf Wildenhues wrote:
> * Allan Caffee wrote on Wed, Feb 25, 2009 at 12:43:02AM CET:
> > Although I must admit I'm not sure what he means by
> > > > [...] this shouldn't matter for read-only trees iff your
> > > > dependencies ar
What is the cleanest to way to append something to a builtin variable
(e.g. MAINTAINERCLEANFILES) from an Automake "header". For example I
want all of my Makefiles to delete the Makefile.in by the
maintainer-clean target. The way I currently do this is:
--- am/global.am ---
GLOBAL_MAINT
On Mon, 23 Feb 2009, Tavian Barnes wrote:
> 2009/2/23 Ralf Wildenhues :
> [...]
> > generated.c can live in the source or in the build tree. But given that
> > different make implementations have slightly different VPATH semantics,
> > it may be useful to require it to always live in the source tr
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
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
16 matches
Mail list logo
