Follow-up Comment #8, bug #65600 (group make):
[comment #7 comment #7:] > You can check the build system of the Linux man-pages, which I wrote in the last few years, if you're interested. It's quite complex, though, so it may be scary. :) > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/> > > The makefiles are the GNUmakefile, and files under share/mk/. Indeed the structure seems complicated to me. I browsed a bit and I like that you have an optional $(INFO_) that can prepend strings to the info lines which helps (I believe) with the hierarchy of the $(info) messages from different makefiles. > Doesn't verilator(1) allow running the compilation in a separate step? Maybe you can do something like this (pseudocode): > > verilator build A >/dev/null > verilator run A > verilator build B >/dev/null > verilator run B > ... Indeed the tool supports separating the generation of makefiles. Then I can make(1) myself. Thanks :) > You could do something similar, and suffix every command with $(STDOUT), and then (conditionally?) define STDOUT:= as an empty thing (so under normal conditions you see the output, and optionally do the same with stderr. When running under verilator, you could define those variables to 1>/dev/null and 2>/dev/null. Good idea! Thanks Alex. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?65600> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
