Hi Derek, Derek wrote: > I would like to replace existing C/VPI code that > interacts with the simulator with Ruby using > ruby-vpi. This would involve loading/running some > verilog, setting callbacks, and accessing the design > hierarchy. > > How could I do this that doesn't involve writing > specifications, test runners, etc as given in the > current documentation?
With the 19.0.0 release this is not possible. However, I did implement part of this feature a while back (I just need to write the documentation now): http://rubyforge.org/pipermail/ruby-vpi-discuss/2007-September/000077.html http://rubyforge.org/pipermail/ruby-vpi-discuss/2007-October/000081.html The basic idea is that the test runner invokes a user-defined Ruby script, which then does whatever it wants with Ruby-VPI. However, if you want to get rid of the test runner as well, I will need to provide two separate .so files: one containing vlog_startup_routines and one without. You could then use the .so file w/o that symbol to embed Ruby-VPI into an existing C/VPI application. I think this is a good approach to pursue. I will make a 20.0.0 release this week containing whatever I implemented so far. The following release, I'll provide the two separate .so files.
