[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Andras Kovi
Subject: [bug #59318] Add option ('-g') of generating build graph for updated goals
Date: Sat, 14 Nov 2020 11:47:22 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0

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


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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]