eine on master
readme: update shield syntax (b… (compare)
some years ago GHDL was distributed as a Debian package, but because it included non-free IEEE libs it was removed. Then, Tristan wrote openieee to allow a roughly functional package of GHDL + libs to be distributed through Debian repos. Now that IEEE libs are open source, openieee should not be required.
Ahhh okay, I see. Probably explains why I had so many difficulties with GHDL a few years ago when I first tried to use it. Thanks for the history!
=== Command output: === /usr/bin/ghdl-mcode:warning: library ieee does not exists for v08 /usr/local/lib/python3.7/dist-packages/vunit/vhdl/string_ops/src/string_ops.vhd:9:9: cannot find resource library "ieee" /usr/local/lib/python3.7/dist-packages/vunit/vhdl/string_ops/src/string_ops.vhd:10:10: unit "std_logic_1164" not found in library "ieee" Compile failed
--export-jsonto get started with
rust_hdl. I have done neither before, so I'm having trouble helping him. VUnit is choking on the vendor libraries. Their location is called out in the
modelsim.inifile, and there are no complaints when simulating the design. But when he tried to
--export-json, VUnit says it can't find the libraries.
$PATH, and now it works. I compared both package contents (Arch and Ubuntu) to the manually installed files, and there are binary
(*.o)and VHDL files missing. Thanks for your help. :)
add_config? I'm looking to retrieve the name so I can pass it to the file_handler parameters. I've checked the documentation but the only information that I've found that could be extracted from the runner are
@eine well I would use GHDL and even contribute, but it's impossible to use with vivado, because ofc all their macros are SV
You can use GHDL as a preprocessor to write VHDL 2008 designs and have them implemented by Vivado. This is not the issue that motivated this conversation (since running VUnit requires unsupported VHDL 1993 features). But it is a work around some other poor features of Vivado.