Closed Paebbels closed 2 years ago
With the Dev release, you can do this with SetExtendedSimulateOptions "--wave=\${LibraryUnit}.ghw"
I think it should get evaluated as a variable. We will have to test it. @Paebbels Please test the above.
Please note, --wave
is a runtime option, so it must be specified after the ${LibraryUnit}
.
See https://ghdl.github.io/ghdl/using/InvokingGHDL.html#elaborate-and-run-elab-run
I think this is now covered by SetExtendedSimulateOptions
.
How to set a single and how to set multiple options? The documentation mentions only a single value.
Examples:
--wave=Testbench.ghw
--wave=Testbench.ghw --stop-time=100us
SetExtendedElaborateOptions, SetExtendedRunOptions, and SetSaveWaves were on main branch. Still have to add documentation for them.
It doesn't appear in the documentation at https://github.com/PLC2/OSVVM-Scripts/blob/main/README.rst, right?
Please add an option to GHDL, so waveform files in GHW format can be created. These can then be viewed and analyzed with GTKwave.
The needed option is
--wave=${LibraryUnit}.ghw
after theLibraryUnit
.Here a diff from my workaround:
Ideally, OSVVM scripting could offer a GUI mode / switch / variable.
vlib/vcom/vsim
interface compatible simulator: launch simulator in GUI mode.