> The actual advantage of your macro comes of course with config.status
> updates - I hope that I can at one day turn my macro into a form that
> adds its -config file output-generation into config.status. IIRC the
> new autoconf does support some helper routines for exactly that purpose.
> But it
Roger Leigh wrote:
>
> I have attached a rewritten ac_path_generic.m4 (AM_PATH_LIB), as well
> as an updated AM_CONFIG_LIBCONFIG. If they are OK, I'm willing to
> submit them to the archive. Any comments appreciated.
Hi Roger,
it took me a bit to get time to have a look - AFAICS your macro a
On Mon, Jul 23, 2001 at 02:01:02AM +0200, Guido Draheim wrote:
> There is a generic-config macro that I'm using quite often. However it
> does not implant code into config.status - it would be best to have
> that done somehow. Anyway, check the m4 source in the ac-archive under:
> http://www.gnu.o
On Mon, Jul 23, 2001 at 02:01:02AM +0200, Guido Draheim wrote:
>
> Tim Van Holder wrote:
> >
> > > Nowadays, many shared libraries include a -config script e.g. libgtk
> > > [...]
> > > There is much duplication of code here. Anyone wishing to use this
> > > scheme must duplicate the script and
Tim Van Holder wrote:
>
> > Nowadays, many shared libraries include a -config script e.g. libgtk
> > [...]
> > There is much duplication of code here. Anyone wishing to use this
> > scheme must duplicate the script and then amend it for their use, and
> > also convert the m4 macro as well, to A
> Nowadays, many shared libraries include a -config script e.g. libgtk
> has a gtk-config script, and a companion m4 macro AM_PATH_GTK. The
> header also has version information embedded in it, as does the
> library itself:
>
> #define _MAJOR_VERSION (@_MAJOR_VERSION@)
> #define _MINOR_VER
