|
|
|
@ -56,7 +56,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
library and ngspice as a tcl/tk library. |
|
|
|
|
|
|
|
Compilation to 64 bit is recommended and available per default in |
|
|
|
the ./compile_linux.sh compule script. 32 bit might be possible, |
|
|
|
the ./compile_linux_new.sh compile script. 32 bit might be possible, |
|
|
|
but is not tested. |
|
|
|
|
|
|
|
The following software must be installed in your system to compile |
|
|
|
@ -64,7 +64,8 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
output): |
|
|
|
bison, flex, X11 headers and libs, Xaw, Xmu, Xext, Xft, FontConfig, |
|
|
|
Xrender, freetype headers and readline. |
|
|
|
Typically one needs the headers (e.g. libX11-devel) and the libs (e.g. libX11-6). |
|
|
|
Typically one needs the headers (e.g. libX11-devel) and the libs (e.g. libX11-6) |
|
|
|
of the packages mentioned above. |
|
|
|
|
|
|
|
ngspice as a shared library (no graphics and no command-line interfaces) |
|
|
|
will need bison and flex only. |
|
|
|
@ -73,11 +74,11 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
internal fft algorithms. |
|
|
|
|
|
|
|
If you want to compile the source from the git repository, or if you want to |
|
|
|
use the compile script ./compile_linux.sh, you will need additional software: |
|
|
|
use the compile script ./compile_linux_new.sh, you will need additional software: |
|
|
|
autoconf, automake, libtool. |
|
|
|
|
|
|
|
The following software may be needed when enabling additional features: |
|
|
|
editline, tcl/tk. |
|
|
|
editline (as a replacement for readline), tcl/tk (when compiling tclspice). |
|
|
|
|
|
|
|
Please have a look at the current ngspice manual, downloadable at |
|
|
|
http://ngspice.sourceforge.net/docs.html, which gives you much more |
|
|
|
@ -86,20 +87,20 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
For compiling ngspice as a shared library, see section 1.4. |
|
|
|
|
|
|
|
|
|
|
|
1.2 Install from tarball (e.g. ngspice-41.tar.gz) |
|
|
|
1.2 Install from tarball (e.g. ngspice-43.tar.gz) |
|
|
|
|
|
|
|
This covers installation from a release distribution (for example |
|
|
|
ngspice-41.tar.gz, the so called tar ball). |
|
|
|
ngspice-43.tar.gz, the so called tar ball). |
|
|
|
|
|
|
|
After downloading the tar ball to a local directory, unpack it by command: |
|
|
|
|
|
|
|
$ tar -zxvf ngspice-41.tar.gz |
|
|
|
$ tar -zxvf ngspice-43.tar.gz |
|
|
|
|
|
|
|
Now change directories in to the top-level source directory (where this |
|
|
|
INSTALL file can be found). |
|
|
|
|
|
|
|
The most comfortable way to compile ngspice is running the compile script |
|
|
|
compile_linux.sh within the terminal window by ./compile_linux.sh. The |
|
|
|
compile_linux.sh within the terminal window by ./compile_linux_new.sh. The |
|
|
|
script has to be declared as 'executable', and admin |
|
|
|
rights are required to allow the installation of ngspice. |
|
|
|
|
|
|
|
@ -110,32 +111,28 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
|
|
|
|
$ mkdir release |
|
|
|
$ cd release |
|
|
|
$ ../configure --with-x --with-readline=yes --disable-debug |
|
|
|
$ ../configure --with-x |
|
|
|
$ make |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
The default install directory for executables is /usr/local/bin, the XSPICE |
|
|
|
code models will be installed in /usr/local/lib/ngspice. Some distros use lib64 |
|
|
|
instead. |
|
|
|
|
|
|
|
A simple ../configure might be sufficient for a basic ngspice, but the preferred |
|
|
|
arguments to ../configure are |
|
|
|
--with-x --with-readline=yes and --disable-debug |
|
|
|
providing you with a comfortably working ngspice. |
|
|
|
|
|
|
|
See the section 1.5 titled 'Advanced Install' for instructions about additional arguments |
|
|
|
that can be passed to ../configure to customise the build and installation. |
|
|
|
instead. The following options are now included automatically: readline, openmp, |
|
|
|
osdi, xspice. Only CIDER has to be selected as an extra option. |
|
|
|
|
|
|
|
A fully featured ngspice on LINUX may be obtained with the following commands: |
|
|
|
$ mkdir release |
|
|
|
$ cd release |
|
|
|
$ ../configure --with-x --enable-xspice --disable-debug --enable-cider --with-readline=yes --enable-predictor --enable-osdi --enable-openmp |
|
|
|
$ ../configure --with-x --enable-cider --enable-predictor |
|
|
|
$ make 2>&1 | tee make.log |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
To remove the executables and libraries from the install directory, you may call |
|
|
|
$ sudo make uninstall |
|
|
|
|
|
|
|
To disable one of the already inlcuded options, you may call --with-readline=no, or |
|
|
|
--disable-openmp, --disable-osdi, --disable-xspice |
|
|
|
|
|
|
|
|
|
|
|
1.3 Install from the git repository |
|
|
|
|
|
|
|
@ -155,7 +152,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
directory, so to e.g. maintain separate debug and release versions. |
|
|
|
|
|
|
|
The most comfortable way to compile ngspice is running the compile script |
|
|
|
compile_linux.sh within the terminal window by ./compile_linux.sh. Admin |
|
|
|
compile_linux_new.sh within the terminal window by ./compile_linux_new.sh. Admin |
|
|
|
rights are required to allow the installation included in the script. |
|
|
|
|
|
|
|
If you want to copile ngspice manually, you may run |
|
|
|
@ -163,7 +160,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
$ ./autogen.sh |
|
|
|
$ mkdir debug |
|
|
|
$ cd debug |
|
|
|
$ ../configure --with-x --with-readline=yes |
|
|
|
$ ../configure --with-x |
|
|
|
$ make |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
@ -178,7 +175,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
$ ./autogen.sh |
|
|
|
$ mkdir release |
|
|
|
$ cd release |
|
|
|
$ ../configure --with-x --enable-xspice --disable-debug --enable-cider --with-readline=yes --enable-openmp --enable-predictor --enable-osdi |
|
|
|
$ ../configure --with-x --enable-cider --enable-predictor |
|
|
|
$ make 2>&1 | tee make.log |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
@ -189,7 +186,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
1.4 ngspice as a shared library |
|
|
|
|
|
|
|
The relevant configure options for the ngspice shared library are: |
|
|
|
$ --with-ngshared --enable-xspice --disable-debug --enable-cider --enable-osdi --enable-openmp |
|
|
|
$ --with-ngshared --enable-cider |
|
|
|
|
|
|
|
Typically the two aliases libngspice.so, libngspice.so.0 and the compiled |
|
|
|
library libngspice.so.0.0.1 are made. The install locations depend on |
|
|
|
@ -217,15 +214,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
|
|
|
|
1.5.1 Most useful options: |
|
|
|
|
|
|
|
--enable-osdi |
|
|
|
Add the OSDI interface to ngspice. This interface allow to dynamically |
|
|
|
load compiled Veriloag-A compact models. Compiling is done with |
|
|
|
OpenVAF. Thus for the first time ngspice has access to modern |
|
|
|
device models like BSOMBULK or BSIM_CMG. |
|
|
|
|
|
|
|
--enable-cider |
|
|
|
Cider is a mixed-level simulator that couples Spice3 and DSIM |
|
|
|
to simulate devices from their technological parameters. |
|
|
|
(the following are already included) |
|
|
|
|
|
|
|
--enable-xspice |
|
|
|
Enable XSpice enhancements, |
|
|
|
@ -240,11 +229,18 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
Parallelization is done by OpenMP, for MOS models in BSIM3.3.0 |
|
|
|
BSIM4.6.0 and and BSOI4 only. See the ngspice manual for details. |
|
|
|
|
|
|
|
--disable-debug |
|
|
|
This option will remove the '-g' option passed to the compiler |
|
|
|
and add -O2 optimization (instead of default O0). |
|
|
|
This speeds up simulating significantly, and is recommended for |
|
|
|
normal use. |
|
|
|
--enable-osdi |
|
|
|
Add the OSDI interface to ngspice. This interface allow to dynamically |
|
|
|
load compiled Veriloag-A compact models. Compiling is done with |
|
|
|
OpenVAF. Thus for the first time ngspice has access to modern |
|
|
|
device models like BSOMBULK or BSIM_CMG. |
|
|
|
|
|
|
|
|
|
|
|
(the following have to be selected to become available) |
|
|
|
|
|
|
|
--enable-cider |
|
|
|
Cider is a mixed-level simulator that couples Spice3 and DSIM |
|
|
|
to simulate devices from their technological parameters. |
|
|
|
|
|
|
|
--enable-oldapps |
|
|
|
The old apllications ngsconvert ngproc2mod ngmultidec and ngmakeidx |
|
|
|
@ -254,11 +250,11 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
Disable using fftw fast fourier transform library. Use internal |
|
|
|
fft instead. Default is 'yes'. |
|
|
|
|
|
|
|
|
|
|
|
--with-editline=yes |
|
|
|
Enables the use of the BSD editline library (libedit) instead |
|
|
|
of readline. |
|
|
|
See https://www.thrysoee.dk/editline/ |
|
|
|
(requires --with-readline=no) |
|
|
|
|
|
|
|
--enable-shortcheck |
|
|
|
Enables a 'make check' with strongly reduced runtime. Besides some |
|
|
|
@ -494,7 +490,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
automake, libtool, FLEX and BISON, all available with pacman in MSYSS2). |
|
|
|
Some links are given below which describe the procedures. |
|
|
|
|
|
|
|
Installing from the tarball, e.g. ngspice-36.tar.gz, is simple: After |
|
|
|
Installing from the tarball, e.g. ngspice-43.tar.gz, is simple: After |
|
|
|
expanding, you may just run ./compile_min.sh from the ngspice directory. |
|
|
|
|
|
|
|
The default installation location of ngspice is the Windows path |
|
|
|
@ -517,16 +513,11 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
$ make |
|
|
|
$ make install |
|
|
|
|
|
|
|
The most useful options are: |
|
|
|
--enable-xspice |
|
|
|
--enable-cider |
|
|
|
--disable-debug (-O2 optimization, no debug information) |
|
|
|
|
|
|
|
A fully featured ngspice on Windows may be obtained with the following commands: |
|
|
|
$ ./autogen.sh |
|
|
|
$ mkdir release |
|
|
|
$ cd release |
|
|
|
$ ../configure --with-wingui --enable-cider --disable-debug --enable-openmp --enable-xspice --enable-osdi |
|
|
|
$ ../configure --with-wingui --enable-cider --disable-debug |
|
|
|
$ make install |
|
|
|
|
|
|
|
However, to compile code extracted from the git repository the procedure is |
|
|
|
|