Hi Branden, "G. Branden Robinson" <[email protected]> writes:
> By happenstance I noticed the gnulib developers talking about how they > had a GNUMakefile target for generating code coverage reports for you. > > In groff, we don't use GNUMakefiles--we try to use portable Make, and > have largely succeeded. If *BSD makes have gotten current with POSIX > 2024, they may even be able to run these targets. The most exotic thing > I see is the `?=` macro definition operator. The 'maintainer-makefile' module doesn't depend on GNU Make for building programs. It copies a "maint.mk' file with the code coverage rules, among other checks to the repository along with "GNUMakefile". The "GNUMakefile" is relatively small and includes three files, "Makefile", "cfg.mk", and "maint.mk"; in that order. The result is that using GNU Make you will have extra targets meant for maintainers. Users using another 'make' program will still be able to build the programs, without the targets meant for maintainers. You can look at coreutils for an example. Though, I am not sure how well the module will work in projects using C++. Collin
