Re: [V] Re: [PATCH] Make daikon work with Build package

Joachim> -- Formatting discipline to help parsing by build.el. SJT> That's hard with autoconf 2.59, which has its own way of doing SJT> things. I have to admit that I don't know at all how and if one can influence AC_HELP_STRING. As far as I have seen, build.el currently has four regexps, one to identify sections, one to identify the description of one option, and one for enumeration values in that description. If one can shoehorn the expansion of AC_HELP_STRING into that format, it gets parseable for build.el. Joachim> -- Maybe also mentioning the type of option values in Joachim> the message. That is not easy to decipher from the Joachim> build.el source. SJT> What do you mean by "type"? This is a shell script, they're all SJT> strings, technically. I mean the "type" for the customization interface. There are some option values that should be represented as strings (e.g., cc flags), some should be a list of strings (e.g., --with-package-path), some should be 1-of-n selections (boolean options, as a selection dialog with values "auto", "yes", and "no") , some should be n-of-m selections (as clickboxes, e.g., --with-error-checking). build.el must get this information from the output of ./configure --help and I don't see how it could do so currently. But Adrian wrote build.el, maybe he has another approach than the one I'm seeing here. I have only superficially looked at the code. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany