Trepan-Debuggers / Trepan-Debuggers/remake

Allow prefixing all make log messages

Open
#139 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
850
Forks
80
PR merge metrics
No merged PRs in 30d

Description

I have a wrapper that parses all make output. I am trying to create a log of make in this format:

`{cmd: 'echo "foo"', output: '"foo"'}`

The ##>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> lines are easy to parse out.

But when using --debug=verbose or --print-directory there are a lot of these message interspersed:

Reading makefiles...
remake: Entering directory '/Users/Vaughan/dev/fork/+bun/bun'
Updating makefiles...
Updating goal targets...
 File 'vendor' does not exist.
   File 'require' does not exist.
  Must remake target 'require'.
Makefile:603: target 'require' does not exist

I would like every line from the make debug messages to be prefixed with [make] for easier parsing.

[make] Reading makefiles...
[make] remake: Entering directory '/Users/Vaughan/dev/fork/+bun/bun'
[make] Updating makefiles...
[make] Updating goal targets...
[make]  File 'vendor' does not exist.
[make]    File 'require' does not exist.
[make]   Must remake target 'require'.
[make] Makefile:603: target 'require' does not exist

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the debug-output paths used by --debug=verbose and --print-directory, along with the existing make log formatting. Reproduce the sample output and verify that every debug line receives the requested [make] prefix without changing the command output; the issue mentions no specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.