Daniel Jacobowitz wrote: > One of the items on my plate is figuring out the best way to > regenerate the generated .h files after moving them to gnulib. > One way would be at gnulib-tool time, another to have a separate > script and keep updated copies checked in.
gnulib-tool so far has no options to execute arbitrary commands depending on the modules. Think of gnulib-tool only as a way to collect bits of code. In fact, I don't think it would be useful if gnulib-tool would duplicate functionality that is already present through Makefile.am (automake and make). One tool for one purpose. For generated files we have 1) in the Makefile.am section of the module description the rules for generating them, 2) some automake variable assignments. For files which take special tools to generate and are system independent, look at the handling of getdate.c in modules/getdate. For files which can be built with portable tools (sh, sed, awk, ...), look at the module 'string' or many others. Bruno
