@ -790,92 +790,8 @@ copy them from other GNU tools.
(from rework-14 release) to the Windows Operating System. His port relies (from rework-14 release) to the Windows Operating System. His port relies
only on DLLs coming with Windows.only on DLLs coming with Windows.
The following text is the email sent to the users' mailing list describing
his port:
@quotation
Dear all,
I have successfully made a pure Windows port of ng-spice-rework-14
using CYGWIN and MINGW32.
Results are @file{ngspice.exe} and @file{ngnutmeg.exe} which only rely on
dlls coming with MS WINDOWS (tested on WINDOWS ME so far).
Several files have been edited, all above @file{configure.in} to comply with
the autotools from CYGWIN. Other @file{*.c} have been edited and patched with
@code{#ifdef __MINGW32__ ... #endif}. Compared to the CYGWIN port for
WINDOWS only minor modifications have been done. Still the WINDOWS port
from Wolfgang M@:ues is used. The resulting source code should still be
compatible to LINUX or UNIX porting (including autotools). I have however
not tested that.
The changes are attached in @file{mingw.patch.bz2}. This file is also cleaned
a bit compared to @file{my.zip} from my last posting.
This is how I made ngspice with CYGWIN and external MINGW32 with the attached
patches applied to ng-spice-rework-14:
according to
@url{http://www.geocrawler.com/@/lists/3/@/SourceForge/@/6013/0/@/7321042/}
@c note - the '@/' allows TeX to insert a line break if necessary
CYGWIN is installed in @file{C:\cygwin}.
MINGW32 is installed in @file{g:\gcc_mingw}.
@example
$ cd ng-spice-rework-14
$ export PATH="/cygdrive/g/gcc_mingw/bin:$PATH"
$ automake
$ autoconf
$ rm config.cache
$ ./configure --with-windows \
--prefix="/cygdrive/g/gcc_mingw/bin"
$ make clean
$ make 2> make.err
$ cp config.h config_ming.h (for use described below)
@end example
@file{ngspice.exe} is o.k., but @command{make check} does not work (cannot
directly output console into file). I have switched off garbage collection
for the moment because it produces errors as I have already posted. Perhaps
the WINDOWS port of gc6.0 which I made is not yet o.k..
I also tried to make ngspice with CYGWIN and internal MINGW32 coming with
the CYGWIN installation:
@example
$ cd ng-spice-rework-14
$ rm config.cache
$ export CFLAGS="-mno-cygwin -g -O2"
$ export LDFLAGS="-L/lib/mingw"
$ export CPPFLAGS="-I/usr/include/mingw"
$ ./configure --with-windows
$ cp config_ming.h config.h
(use config.h from porting described above)
$ make clean
$ make 2> make.err
@end example
@command{./configure} does not work correctly: It finds headers and libs
which are not really available in the internal port of MINGW32 (flag
@option{-mno-cygwin}), but are useful only in CYGWIN. Therefore the resulting
@file{config.h} is not o.k.. So finally I used @file{config.h} from my port
with external MINGW32 as described above. This was however the only change
necessary to compile succesfully with internal MINGW32.
ToDo: find appropriate presets for variables in @file{configure.in} or
rewrite the autotool tests for headers and libs (search exclusively in
mingw directories and not in the standard directories). Maybe this is
already described in a proper mailing list.
Regards
Holger Vogt
@end quotation
As of Rework-16 the Windows port is integrated as part of ngspice. It can be
build under @url{http://www.cygwin.com/,,Cygwin} or @url{http://www.mingw.org/,,MinGW}.
The situation of NGSPICE ports is evolving continually, the one above are theThe situation of NGSPICE ports is evolving continually, the one above are the
sjborley
21 years ago