From e18598520eb211b218e777dfefa7af98af480faa Mon Sep 17 00:00:00 2001 From: Holger Vogt Date: Sun, 23 Dec 2018 13:43:08 +0100 Subject: [PATCH] Prepare ngspice-30 --- FAQ | 4 ++-- INSTALL | 12 ++++++------ README.adms | 2 +- configure.ac | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/FAQ b/FAQ index e0e61eb74..a79265d58 100644 --- a/FAQ +++ b/FAQ @@ -1,4 +1,4 @@ - Ngspice F.A.Q.Version 2.3 (ngspice-29 release) + Ngspice F.A.Q.Version 2.3 (ngspice-30 release) Maintained by Holger Vogt Last update: 09-14-2018 @@ -241,7 +241,7 @@ The latest version released is: - * ngspice-29 (released on ../../2018) + * ngspice-30 (released on 01/01/2019) 2.2. What are the latest features in the current release? diff --git a/INSTALL b/INSTALL index c69b97447..23a055a5f 100644 --- a/INSTALL +++ b/INSTALL @@ -5,7 +5,7 @@ Table of contents 1 Ngspice installation (LINUX) 1.1 Prerequisites - 1.2 Install from tarball (e.g. ngspice-29.tar.gz) + 1.2 Install from tarball (e.g. ngspice-30.tar.gz) 1.3 Install from git repository 1.4 Advanced Install 1.4.1 Most useful options @@ -53,14 +53,14 @@ This file describes the procedures to install ngspice from sources. information on ngspice and its usage. -1.2 Install from tarball (e.g. ngspice-29.tar.gz) +1.2 Install from tarball (e.g. ngspice-30.tar.gz) This covers installation from a release distribution (for example ngspice-27.tar.gz, the so called tar ball). After downloading the tar ball to a local directory unpack it using: - $ tar -zxvf ngspice-29.tar.gz + $ tar -zxvf ngspice-30.tar.gz Now change directories in to the top-level source directory (where this INSTALL file can be found). @@ -460,8 +460,8 @@ Most of the options now following are not well maintained, are not tested or eve to the standard install (FLEX and BISON have to be made available in MSYS). Some links are given below which describe the procedures. - Installing from the tarball, e.g. ngspice-29.tar.gz, is now simple: After - expanding, you may just run ./compile_min.sh from the ngspice-29 directory. + Installing from the tarball, e.g. ngspice-30.tar.gz, is now simple: After + expanding, you may just run ./compile_min.sh from the ngspice-30 directory. The default installation location of ngspice is the Windows path C:\spice. The install path can be altered by passing --prefix=NEWPATH @@ -475,7 +475,7 @@ Most of the options now following are not well maintained, are not tested or eve The procedure of compiling a distribution (for example, a tarball from the ngspice website), is as follows: - $ cd ngspice-29 + $ cd ngspice-30 $ mkdir release $ cd release $ ../configure --with-wingui ...and other options diff --git a/README.adms b/README.adms index f35063a67..cbda7a84e 100644 --- a/README.adms +++ b/README.adms @@ -29,7 +29,7 @@ admsXml (see below). Unfortunately most of the above named models’ licenses are not compatible to free software rules as defined by DFSG. Therefore since ngspice-28 the va model files are no longer part of the standard ngspice distribution. They may however be downloaded as a tar.gz archive from the -ngspice-29 file distribution folder. After downloading, you may expand the zipped files into +ngspice-30 file distribution folder. After downloading, you may expand the zipped files into your ngspice top level folder. The models enable dc, ac, and tran simulations. Noise simulation is not supported. Other (foreign) va model files will not compile without code tweaking, due to the limited diff --git a/configure.ac b/configure.ac index 84b895140..63361d5b2 100644 --- a/configure.ac +++ b/configure.ac @@ -12,7 +12,7 @@ # --------------- # Initialisation of configure -AC_INIT([ngspice], [29+], [http://ngspice.sourceforge.net/bugrep.html]) +AC_INIT([ngspice], [30], [http://ngspice.sourceforge.net/bugrep.html]) # Unique file in the source directory AC_CONFIG_SRCDIR([src/ngspice.c])