To be able to build and run these examples you will need to set two
environment variables, ARCH and PLIINC
ARCH - must be set to one of the following
linux for a pc running linux
sun4v for a solaris machine
hppa for a HP PA-RISK machine
winnt for either Win-95/98 or WINNT
PLIINC - must be set to contain the path to where the different PLI
include files are stored.
Windows (Win95/Win98/WinNT) need two other environment variabels set
MSDIR - Path to the microsoft compilier. ex D:/msdev/DevStudio
PLILIB - Path to the simulator's import library
ex:
d:/XYZ/tools/verilog/lib/verilog.lib (VerilogXL)
or
d:/XYZ/tools/lib/pliinterface.lib (NC-Verilog)
or
...
NOTE: The assumption is that you are running in something like the
MKS corn shell and have a real make installed in you search
path. Sorry I am a UNIX bigot at heart. Also seeing that I
was able to make one command "make" work on four different
platforms consistency was a good thing.
To get started type:
make
This will walk down to the util directory and build the different
common utility(s) that will be used by the different example(s). When
the build is completed the required libraries/objects will be copied
into the ./lib directory and the required include files into the
directory ./include.
It will then walk into the different PLI example directory(s) and build
the PLI/VPI code used by the exmple(s).
At this point you can cd to the directory vpi or pli /<example> and
read the file "README" in the given directory.
When you are done playing around and want to clean up you can type
make clean
from this directory. All the generated file will be removed.
**********************************************************************
All the include/Makefile/*.c/*.h files in this directory and lower
directories are free for the taking with no restriction on their usage
being imposed and or implied. While some testing has been done to
make sure the basic functionality works no guarantees are being made
either.
enjoy
