Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow prefixing all make log messages #139

Open
vjpr opened this issue Nov 15, 2022 · 1 comment
Open

Allow prefixing all make log messages #139

vjpr opened this issue Nov 15, 2022 · 1 comment

Comments

@vjpr
Copy link

vjpr commented Nov 15, 2022

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
@rocky
Copy link
Collaborator

rocky commented Nov 15, 2022

One of the cool things about this project is that can be a springboard for trying out various ideas.

It looks like this line is the single place that would need to change.

Try changing that in a locally checkout out source. If that works and you are up for it see if you can work that into an additional flag passed on invocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants