[bug #59318] Add option ('-g') of generating build graph for updated goals

[Andras Kovi]

Follow-up Comment #3, bug #59318 (project make):

Hi!

Nice proposal. The Remake project (http://bashdb.sourceforge.net/remake/)
already implements something like this. We even tried it on our project.

The problem I found with that feature is that the resulting graph can be
incomprehensibly large (millions of nodes for large projects) and therefore
not very useful in reality. In the end, we figured out that the easiest way to
ensure that we can identify why something is being remade is to add basic
logging to all make runs (--debug=b). This shows very minimal details, does
not distort the logs too much but provides the vital info required to identify
the root cause in most cases.

On the other hand, such a graph can be really useful to discover dependencies
and use it to optimize the build. Of course, that requires proper tooling for
the graph handling.

Have you tried the Remake implementation? Did you find it useful in practice?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59318>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/