Provide "COCOTB_SIM_DEBUG" Makefile variable
See original GitHub issueFor the kind of debugging work in #639, it would be good to have a documented Makefile variable like COCOTB_SIM_DEBUG
which would switch options like Cadence Incisive/Xcelium’s -plinowarn
and -pliverbose
.
Does anyone know examples of such switches for other simulators?
Example code:
ifeq ($(COCOTB_SIM_DEBUG),1)
EXTRA_ARGS += -pliverbose
EXTRA_ARGS += -messages
else
EXTRA_ARGS += -plinowarn
endif
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
GNU make - How to Use Variables
A variable is a name defined in a makefile to represent a string of text, called the variable's value. These values are substituted...
Read more >Passing additional variables from command line to make
You have several options to set up variables from outside your makefile: From environment - each environment variable is transformed into a makefile...
Read more >Setting a Makefile Variable From Outside the Makefile
A simple way to handle this is with a Makefile variable called BUILD_DEBUG which is set to yes in the Makefile and overriden...
Read more >Build options and Environment Variables
Typically the makefiles provided with cocotb for various simulators use a separate compile and run target. This allows for a rapid re-running of...
Read more >3. Variables and Macros - Managing Projects with GNU Make ...
There are two other assignment operators provided by make . The ?= operator is called the conditional variable assignment operator. That's quite a...
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
Closing as we want to get rid of as many variables as possible, see #1495.
@wallento What do you think about the idea of throwing together
VERILATOR_SIM_DEBUG
andVERILATOR_TRACE
underCOCOTB_SIM_DEBUG
?