Re: [Ngspice-devel] tclspice for windows

[Holger V. <hol...@un...>]

Hi all,

it is true that I can compile ngspice without tcl under mingw right now 
using CVS sources, however compilation is very slow.

The following excerpt from the "make install" log file shows why: each 
file is currently compiled two times! The same happens in a pure CYGWIN 
build.

if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H 
-I. -I. -I../../..  -I../../../src/include   -g -O2 -O2 -Wall -mwindows 
-MT niconv.lo -MD -MP -MF ".deps/niconv.Tpo" -c -o niconv.lo niconv.c; \
then mv -f ".deps/niconv.Tpo" ".deps/niconv.Plo"; else rm -f 
".deps/niconv.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/include -g -O2 
-O2 -Wall -mwindows -MT niconv.lo -MD -MP -MF .deps/niconv.Tpo -c 
niconv.c  -DDLL_EXPORT -DPIC -o .libs/niconv.o
 gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/include -g -O2 
-O2 -Wall -mwindows -MT niconv.lo -MD -MP -MF .deps/niconv.Tpo -c 
niconv.c -o niconv.o >/dev/null 2>&1

which is probably wanted and reflected in the entry to niconv.lo.

# Name of the PIC object.
pic_object='.libs/niconv.o'

# Name of the non-PIC object.
non_pic_object='niconv.o'

What is this all about?
Why do we need such a major change to the build procedure? Why do we 
need to introduce *.lo and *.la?
The tcl options is not ready anyway.
Working on ngspice under Windows currently is not very pleasant.

Regards

Holger



Holger Vogt schrieb:
> Hi all,
>
> the windows version builds again (without tcl).
>
>   
...