Makefiles write to sim.log inconsistently
See original GitHub issueOur Makefile.ghdl
doesn’t have the usual | tee $(SIM_BUILD)/sim.log
at the end of the simulation command line nor any other option to that effect, so it doesn’t produce a sim.log
file at all.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Tutorial on writing makefiles
Tutorial on writing makefiles. Do I need a makefile? A simple makefile. Using variables; Pattern rules. Phony targets; Working with several directories.
Read more >GNU make
GNU make. This file documents the GNU make utility, which determines automatically which pieces of a large program need to be recompiled, ...
Read more >Build options and Environment Variables
The common Makefile cocotb/share/makefiles/Makefile.sim includes the appropriate simulator Makefile based on the contents of the SIM variable.
Read more >Vivado Simulator scripted flow Part 3: Makefiles - It's Embedded!
When writing a Makefile, most targets are named exactly as the output file that the target recipe produces. Dependencies of targets can be ......
Read more >12. Debugging Makefiles - Managing Projects with GNU Make ...
Normally, debugging information is not enabled until after the makefiles have been updated. This includes updating any included files, such as lists of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, this file
sim.log
is only used in about 50% of our Makefiles, the other ones are letting the simulator write whatever file it likes. Since the| tee
is breaking theisatty
detection for color output, we should rather try to remove this.Yeah I’ll try to track it down more precisely and make an issue