diff --git a/verilog.spec b/verilog.spec index fd0749829..39eb4d5d5 100644 --- a/verilog.spec +++ b/verilog.spec @@ -35,6 +35,7 @@ make prefix=$RPM_BUILD_ROOT/usr install %attr(-,root,root) %doc examples/* %attr(-,root,root) /usr/man/man1/iverilog.1.gz +%attr(-,root,root) /usr/man/man1/vvp.1.gz %attr(-,root,root) /usr/bin/iverilog %attr(-,root,root) /usr/bin/vvp diff --git a/vvp/Makefile.in b/vvp/Makefile.in index 3958a871b..0fddd2cb5 100644 --- a/vvp/Makefile.in +++ b/vvp/Makefile.in @@ -16,7 +16,7 @@ # 59 Temple Place - Suite 330 # Boston, MA 02111-1307, USA # -#ident "$Id: Makefile.in,v 1.24 2001/06/21 22:54:12 steve Exp $" +#ident "$Id: Makefile.in,v 1.25 2001/07/21 04:34:25 steve Exp $" # # SHELL = /bin/sh @@ -29,6 +29,7 @@ VPATH = $(srcdir) bindir = @bindir@ libdir = @libdir@ +mandir = @mandir@ includedir = @includedir@ CC = @CC@ @@ -97,16 +98,20 @@ Makefile: Makefile.in config.status ./config.status -install: all installdirs $(bindir)/vvp +install: all installdirs $(bindir)/vvp $(mandir)/man1/vvp.1 $(bindir)/vvp: ./vvp $(INSTALL_PROGRAM) ./vvp $(bindir)/vvp +$(mandir)/man1/vvp.1: $(srcdir)/vvp.man + $(INSTALL_DATA) $(srcdir)/vvp.man $(mandir)/man1/vvp.1 + installdirs: $(srcdir)/mkinstalldirs - $(srcdir)/mkinstalldirs $(bindir) + $(srcdir)/mkinstalldirs $(bindir) $(mandir)/man1 uninstall: rm -f $(bindir)/vvp + rm -f $(mandir)/man1/vvp.1 -include $(patsubst %.o, dep/%.d, $O) diff --git a/vvp/vvp.man b/vvp/vvp.man new file mode 100644 index 000000000..86f60eabf --- /dev/null +++ b/vvp/vvp.man @@ -0,0 +1,49 @@ +.TH vvp 1 "$Date: 2001/07/21 04:34:25 $" Version "$Date: 2001/07/21 04:34:25 $" +.SH NAME +vvp - Icarus Verilog vvp runtime engine + +.SH SYNOPSIS +.B vvp +[-dv] [-Mpath] [-mmodule] inputfile + +.SH DESCRIPTION +.PP +\fIvvp\fP is the run time engine that executes the default compiled +form generated by Icarus Verilog. The output from the \fIiverilog\fP +command is not by itself executable on any platform. Instead, the +\fIvvp\fP program is invoked to execute the generated output file. + +.SH OPTIONS +.l +\fIvvp\fP accepts the following options: +.TP 8 +.B -M\fIpath\fP +This flag specifies the directory to use to locate VPI modules. This +is normally not used as the installer places the modules in the +default directory, but it can be used if you choose to use alternate +versions of VPI modules. +.TP 8 +.B -m\fImodule\fP +Tell the vvp run time to load the named module before executing the +simulation. The \fBsystem.vpi\fP module is loaded by default, but +additional modules, including modules that you compiled locally, can +be specified with this flag. Any number of modules can be loaded, and +they will be linked in the order they are listed on the command line. +.TP 8 +.B -v +Turn on verbose messages. This will cause information about run time +progress to be printed to standard out. + +.SH "AUTHOR" +.nf +Steve Williams (steve@icarus.com) + +.SH SEE ALSO +.BR "" + +.SH COPYRIGHT +.nf +Copyright \(co 2001 Stephen Williams + +This document can be freely redistributed according to the terms of the +GNU General Public License version 2.0