Karl Berry wrote: > Would it be at all feasible for gnulib to support non-automake (just > autoconf) projects? If the answer is "not at all feasible", that's ok. > I'm just asking, not requesting.
gnulib can be used in projects which don't use Makefile.am so far. But gnulib-tool will create the first Makefile.am in this case. An example of a package in this situation is GNU libiconv, where the only Makefile.am is in srclib/, essentially generated by gnulib-tool: http://git.savannah.gnu.org/gitweb/?p=libiconv.git;a=tree > (I have a potential GNU package whose maintainer already knows autoconf, > but not automake. It would be nice if he could use gnulib-tool and all > the myriad of gnulib code.) He can do so without learning how to write a Makefile.am and how to use the AM_* macros. But he will have to learn how to invoke the 'automake' command. Bruno
