luke
/
ngspice
mirror of https://git.code.sf.net/p/ngspice/ngspice
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

how-to-ngspice-vstudio.txt, update for use with cuda

This commit is contained in:
Holger Vogt 2017-10-08 15:17:54 +02:00 committed by rlar
parent e32af75d62
commit 4ceb4ed8eb
1 changed files with 14 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
visualc/how-to-ngspice-vstudio.txt
View File

@ -1,4 +1,5 @@
ngspice may be compiled by MS Visual Studio Community 2015. ngspice for cuda may be compiled by MS Visual Studio Community 2015.
VS 2017 is not compatible with cuda 8.0 (you will have to wait for 9.0).
For compilation you need the GNU bison parser generator. For compilation you need the GNU bison parser generator.
@ -13,60 +14,30 @@ relative from this directory right here, and unzip there.
We will invoke the win_bison.exe file We will invoke the win_bison.exe file
in this directory during the visual studio compilation. in this directory during the visual studio compilation.
Install CUDA 8.0 from
https://developer.nvidia.com/cuda-downloads
Visual Studio is started by double click on vngspice.sln. Visual Studio is started by double click on cuspice.sln.
Select 'Build' 'Configuration Manager' and then choose one Select 'Build' 'Configuration Manager' and then choose one
of the build options, e.g. 'Active solution configuration' of the build options, e.g. 'Active solution configuration'
with its Debug, Release or ReleaseOMP GUI versions or the with its Debug or Release GUI versions or the
equivalent console version (no GUI, no graphical interface), equivalent console version (no GUI, no graphical interface),
and 'Active solution platform', generating either 32 bit code and 'Active solution platform', generating 64 bit code only.
by choosing 'x86', or 64 bit code by 'x64'.
Selection of 'Build' and then 'Rebuild solution' will build XSPICE and CIDER is not supported by cuspice.
complete ngspice, starting with XSPICE, where cmpp.exe is made
first, then all code models are compiled as dlls named *.cm,
and and afterwards ngspice.exe is generated. Finally
make-install-vngspice.bat is called to copy ngspice.exe, code
models and spinit into a directory tree, that resembles the one
generated by mingw 'make install'. An example tree for
ReleaseOMP 32 bit is given below.
C:\Spice\ Installation procedure will generate the following tree:
C:\Spice64\
bin\ bin\
ngspice.exe ngspice.exe
vcomp140.dll vcomp140.dll
lib\
spice\
analog.cm
digital.cm
spice2poly.cm
extradev.cm
extravt.cm
table.cm
share\ share\
ngspice ngspice
scripts\ scripts\
spinit spinit
C:\Spice64\ may be renamed to any folder with rights for read and write.
If spinit is not found in the directory cited above, If spinit is not found in the directory cited above,
ngspice.exe also searches for spinit in its own directory. If you ngspice.exe also searches for spinit in its own directory.
give a relative path for the codemodel directories in spinit, you
may define your own directory tree.
The dll version of ngspice, ngspice.dll, is made as a standalone
dll (no codemodels, no installation) by double click on
sharedspice.sln. However ngspice.dll may use the directory
tree and code models as created above.
If you want to add fftw support for the fft commands, download
the Windows variant of fftw from
http://www.fftw.org/install/windows.html.
Create the directories
../../fftw-3.3.4-dll32
../../fftw-3.3.4-dll64
relative from this directory right here, and unzip there the
32 bit and 64 bit downloads.
Visual Studio is stated by double click on vngspice-fftw.sln.
The following procedure is the same as cited above.