|
|
|
@ -1,8 +1,9 @@ |
|
|
|
Ngspice installation instructions |
|
|
|
================================= |
|
|
|
|
|
|
|
Important notice: since ngspice-39 there has been an update |
|
|
|
to the XSPICE code models (analog.cm etc.). Therefore it |
|
|
|
Important notice: If you upgrade from ngspice-38 or older |
|
|
|
there there is an update required for the XSPICE code |
|
|
|
models (analog.cm etc.). Therefore it |
|
|
|
is not sufficient to only re-make the main executable, |
|
|
|
you will have to compile and install the code models as well, |
|
|
|
e.g. with --enable-xspice. |
|
|
|
@ -50,16 +51,20 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
is needed. Almost any LINUX offers a complete C development environment. |
|
|
|
Ngspice is developed on GNU/Linux with gcc and GNU make. |
|
|
|
|
|
|
|
Ngspice may be compiled in three different variant, each with its own |
|
|
|
Ngspice may be compiled in three different variants, each with its own |
|
|
|
configure settings. Standard ngsoice executable, ngspice as a shared |
|
|
|
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, |
|
|
|
but is not tested. |
|
|
|
|
|
|
|
The following software must be installed in your system to compile |
|
|
|
ngspice as a standard executable (command-line input, file and graphics |
|
|
|
output): |
|
|
|
bison, flex, X11 headers and libs, Xaw, Xmu, Xext, Xft, FontConfig, |
|
|
|
Xrender, and freetype headers (e.g. libX11-devel) and libs (e.g. libX11-6), |
|
|
|
and readline. |
|
|
|
Xrender, freetype headers and readline. |
|
|
|
Typically one needs the headers (e.g. libX11-devel) and the libs (e.g. libX11-6). |
|
|
|
|
|
|
|
ngspice as a shared library (no graphics and no command-line interfaces) |
|
|
|
will need bison and flex only. |
|
|
|
@ -81,21 +86,22 @@ 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-40.tar.gz) |
|
|
|
1.2 Install from tarball (e.g. ngspice-41.tar.gz) |
|
|
|
|
|
|
|
This covers installation from a release distribution (for example |
|
|
|
ngspice-40.tar.gz, the so called tar ball). |
|
|
|
ngspice-41.tar.gz, the so called tar ball). |
|
|
|
|
|
|
|
After downloading the tar ball to a local directory, unpack it by command: |
|
|
|
|
|
|
|
$ tar -zxvf ngspice-40.tar.gz |
|
|
|
$ tar -zxvf ngspice-41.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. Admin |
|
|
|
rights are required to allow the installation included in the script. |
|
|
|
compile_linux.sh within the terminal window by ./compile_linux.sh. The |
|
|
|
script has to be declared as 'executable', and admin |
|
|
|
rights are required to allow the installation of ngspice. |
|
|
|
|
|
|
|
CentOS users may need to add -std=c99 to the CFLAGS in the ../configure |
|
|
|
statement. |
|
|
|
@ -108,7 +114,9 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
$ make |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
The default install directory for executables is /usr/local/bin. |
|
|
|
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 |
|
|
|
@ -121,7 +129,7 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
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-osdi --enable-openmp |
|
|
|
$ ../configure --with-x --enable-xspice --disable-debug --enable-cider --with-readline=yes --enable-predictor --enable-osdi --enable-openmp |
|
|
|
$ make 2>&1 | tee make.log |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
@ -170,7 +178,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-osdi |
|
|
|
$ ../configure --with-x --enable-xspice --disable-debug --enable-cider --with-readline=yes --enable-openmp --enable-predictor --enable-osdi |
|
|
|
$ make 2>&1 | tee make.log |
|
|
|
$ sudo make install |
|
|
|
|
|
|
|
@ -291,10 +299,8 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
--enable-cpdebug |
|
|
|
Enable ngspice shell code debug. |
|
|
|
|
|
|
|
--disable-debug |
|
|
|
This option will remove the '-g' option passed to the compiler. |
|
|
|
This speeds up compilation a *lot*, and is recommended for |
|
|
|
normal use. |
|
|
|
--disable-sp |
|
|
|
Disable S Parameter Analysis |
|
|
|
|
|
|
|
--enable-ftedebug |
|
|
|
Enable ngspice frontend debug. |
|
|
|
@ -602,9 +608,8 @@ This file describes the procedures to install ngspice from sources. |
|
|
|
CIDER and XSPICE are included, the code models for XSPICE |
|
|
|
(*.cm) are made as well. |
|
|
|
|
|
|
|
There is currently no installation procedure provided, you may |
|
|
|
however install the executable manually as described in the |
|
|
|
installation tree below. |
|
|
|
ngspice is installed into C:\Spice64\ (release version) or |
|
|
|
C:\Spice64d\ (debug version). |
|
|
|
|
|
|
|
The directory (visualc) with its files |
|
|
|
vngspice.sln (project starter) and |
|
|
|
|
Holger Vogt
3 years ago