Follow-up Comment #12, bug#64571 (group make):
Wow, that's great stuff from Tim. I was really re-treading his steps there,
even with the same flag name `--print-data-base-json`!
Definitely valid limitations of nested JSON, very tricky to parse without the
right tools. However, in this context, is
Follow-up Comment #10, bug#64571 (group make):
@psmith, just missed your comment while I was writing mine :) Seems like we
were thinking in a similar direction, I agree the `--format` option is a good
fit with how other tools handle this.
When I get a chunk of time, I can put in a proposal for th
Follow-up Comment #9, bug#64571 (group make):
I had a thought about how this could be approached in a different way.
As has been mentioned, we already have a lot of information available about
targets (also variables and other info) via the `--print-data-base` flag. It's
just that as it currently
Follow-up Comment #1, bug #64571 (project make):
I'm also interested in this feature. I often find when coming back to an old
project I want a quick way to list the possible targets so that I remember
what `make` invocation I should run. Especially for .PHONY targets that are
just performing some
