>>>> "Joachim" == Joachim Schrod
<jschrod(a)acm.org> writes:
Joachim> As far as I have seen, build.el currently has four
Joachim> regexps, one to identify sections, one to identify the
Joachim> description of one option, and one for enumeration values
Joachim> in that description. If one can shoehorn the expansion of
Joachim> AC_HELP_STRING into that format, it gets parseable for
Joachim> build.el.
The tail is wagging the dog, here. The less we mess with the autoconf
code, the better. I'm not even happy about merging --enable-foo with
--with-foo although that's obviously TheRightThang[tm].
Joachim> I mean the "type" for the customization interface. There
Joachim> are some option values that should be represented as
Joachim> strings (e.g., cc flags), some should be a list of
Joachim> strings (e.g., --with-package-path), some should be
Joachim> 1-of-n selections (boolean options, as a selection dialog
Joachim> with values "auto", "yes", and "no") , some
should be
Joachim> n-of-m selections (as clickboxes, e.g.,
Joachim> --with-error-checking).
All of this is available in configure.ac.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.