[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autocache
From: |
Ralf Wildenhues |
Subject: |
Re: autocache |
Date: |
Sat, 2 Apr 2011 09:58:37 +0200 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
* Alfred M. Szmidt wrote on Fri, Apr 01, 2011 at 11:10:43PM CEST:
> Then, how did you come up with the list of gnulib modules in
> bootstrap.conf and the list of macros to call in configure.ac?
> Ideally, they should not generated and not specified manually, that
> will only lead to bit rot. If needed, then it is more useful to
> specify exceptions manually.
>
> I first extracted all modules from gnulib, and went over them manually
> to figure out what is "sensible"; with a very vauge definition of
> "sensible". Not sure what the best way is to extract them.
Just generating a list of macros could be done in a number of ways:
- autoconf --trace the macro files, grep for public API namespace,
use an exclusion list like autoconf/tests/mktests.sh does.
- For gnulib, grep the modules/* files for used macros (supposedly
those are only public ones), continue with an exclusion list.
Cheers,
Ralf
- Re: autocache, Alfred M. Szmidt, 2011/04/01
- Re: autocache,
Ralf Wildenhues <=