2002-11-23 01:51:53 +01:00
|
|
|
.TH iverilog-vpi 1 "$Date: 2002/11/23 00:51:53 $" Version "$Date: 2002/11/23 00:51:53 $"
|
2002-05-28 07:21:30 +02:00
|
|
|
.SH NAME
|
|
|
|
|
iverilog-vpi - Compile front end for VPI modules
|
|
|
|
|
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.B iverilog-vpi
|
2002-07-05 19:17:20 +02:00
|
|
|
[--name=\fIname\fP]
|
2002-05-28 07:21:30 +02:00
|
|
|
\fIsourcefile\fP...
|
|
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.PP
|
|
|
|
|
\fIiverilog-vpi\fP is a tool to simplify the compilation of VPI
|
|
|
|
|
modules for use with Icarus Verilog. It takes on the command line a
|
|
|
|
|
list of C or C++ source files, and generates as output a linked VPI
|
|
|
|
|
module. See the \fBvvp\fP(1) man page for a description of how the
|
|
|
|
|
linked module is loaded by a simulation.
|
|
|
|
|
|
|
|
|
|
The output is named after the first source file. For example, if the
|
|
|
|
|
first source file is named \fIfoo.c\fP, the output becomes
|
|
|
|
|
\fIfoo.vpi\fP.
|
|
|
|
|
|
|
|
|
|
.SH OPTIONS
|
|
|
|
|
.l
|
|
|
|
|
\fIiverilog-vpi\fP accepts the following options:
|
|
|
|
|
.TP 8
|
|
|
|
|
.B -l\fIlibrary\fP
|
|
|
|
|
Include the named library in the link of the VPI module. This allows
|
|
|
|
|
VPI modules to further reference external libraries.
|
|
|
|
|
|
2002-07-05 19:17:20 +02:00
|
|
|
.TP 8
|
|
|
|
|
.B --name=\fIname\fP
|
|
|
|
|
Normally, the output VPI module will be named after the first source
|
|
|
|
|
file passed to the command. This flag sets the name (without the .vpi
|
|
|
|
|
suffix) of the output vpi module.
|
2002-11-23 01:51:53 +01:00
|
|
|
|
|
|
|
|
.SH "PC-ONLY OPTIONS"
|
|
|
|
|
|
|
|
|
|
The PC port of \fIiverilog-vpi\fP includes two special flags needed to
|
|
|
|
|
support the more intractable development environment. These flags help
|
|
|
|
|
the program locate parts that it needs.
|
|
|
|
|
|
|
|
|
|
.TP 8
|
|
|
|
|
.B -mingw=\fIpath\fP
|
|
|
|
|
Tell the program the root of the Mingw compiler tool suite. The
|
|
|
|
|
\fBvvp\fP runtime is compiled with this compiler, and this is the
|
|
|
|
|
compiler that \fIiverilog-vpi\fP expects to use to compile your source
|
|
|
|
|
code. This is notmally not needed, and if you do use it, it is only
|
|
|
|
|
needed once. The compiler will save the \fIpath\fP in the registry for
|
|
|
|
|
use later.
|
|
|
|
|
|
|
|
|
|
.TP 8
|
|
|
|
|
.B -ivl=\fIpath\fP
|
|
|
|
|
Set for the use during compilation the root if the Icarus Verilog
|
|
|
|
|
install. This is the place where you installed Icarus Verilog when you
|
|
|
|
|
ran the installer. This flag is also only needed once, and the path is
|
|
|
|
|
stored in the registry for future use.
|
|
|
|
|
|
2002-05-28 07:21:30 +02:00
|
|
|
.SH "AUTHOR"
|
|
|
|
|
.nf
|
|
|
|
|
Steve Williams (steve@icarus.com)
|
|
|
|
|
|
|
|
|
|
.SH SEE ALSO
|
|
|
|
|
iverilog(1), vvp(1),
|
2002-11-23 01:51:53 +01:00
|
|
|
.BR "<http://www.icarus.com/eda/verilog/>",
|
|
|
|
|
.BR "<http://www.mingw.org>",
|
2002-05-28 07:21:30 +02:00
|
|
|
|
|
|
|
|
.SH COPYRIGHT
|
|
|
|
|
.nf
|
|
|
|
|
Copyright \(co 2002 Stephen Williams
|
|
|
|
|
|
|
|
|
|
This document can be freely redistributed according to the terms of the
|
|
|
|
|
GNU General Public License version 2.0
|
