Frequently Asked Questions
What license is VRQ released under?
VRQ is released under the GPLv2 license. Currently all the include plugins are GPLv2 as well, however this many not remain the case as any compatible license would be allowed.
Does that prohibit me from using verilog code processed by VRQ in commercial products?
Absolutely not! The intent is provide a useful tool an framework the all may to create HW for commercial, educational or personal benefit.
Can the VRQ lex, parser, etc be included in a commercial SW product?
No VRQ is released under the GPLv2 license and its terms of use must be met. However it is possible to supply VRQ under a different license, please contact the author for details.
Can I write a plugin tool? Is there documentation available regarding the tool API and VRQ internals?
You can certainly write a tool, there have been others who have. However at this time there is no documentation other than the source code to help with this. If you wish to do so the file node.h contains the parse tree node descriptions. Also using one of the existing plugin tools as a template can be most helpful.
Does VRQ support the entire Verilog 2005 standard?
Not completely. There are a few small things like the library constructs that are not currently supported. Note however some of the tools are less complete. For instance the
sim tool is based upon the VeriWell source code which only supports a subset of Verilog 1995.
Does VRQ support System Verilog? If not will it in the future?
Currently VRQ does not support System Verilog constructs. Over time support will be added.
Can the output of one tool be used as the input to another?
Yes. You can use multiple -tool switches on the command line. The output of one tool will be pipelined into the input of the next.