Re: [Ngspice-devel] xspice code into ngspice

[Stefan J. <ste...@mu...>]

This how I integrated the xspice code into tclspice; I did a grep of the
xspice code for "gtri". The xspice people kindly commented all there
changes with that label. I then merged all the additions into tclspice.

So the core code base is totally merged in, and sort of tested by people
at Multigig.

The Spice Opus dependency is now no more as I have ported the old xspice
cmpp into tclspice ( src/xspice/cmpp ) and it produces equivalent code
as the Spice Opus version. All that is needed to be done now is to put
the rest of the codemodels into CVS with appropriate makefiles (ie rip
out of xspice). The codemodels are modular shared libraries so this can
be done as required.

(PS. tclspice was branched off at ng-spice-rework-14, so a diff against
that will give you all my changes / additions )

Stefan

On Mon, 2003-07-07 at 21:14, Paolo Nenzi wrote:
> Dear All,
> 
> I am going to merge some of the tclspice code into ngspice mainstream
> (before committing some work I have done on CIDER and devices). I have
> checked out the main branch code (ng-spice-rework-14) and the TCLSPICE
> branch code.  
> 
> I would like to ask:
> 
> To what extent XSPICE has been included into tclspice ?
>       I mean: I have read the README file which says that users need 
>       to get some code from Spice-OPUS. Is this still true and why ?
> 
> 
> Georgia Tech now have set a download page for xspice code. 
> 
> Has the original GTRI package the necessary functions that will free us
> from the Spice-OPUS dependence ?
> 
> If so (or if this code is available and integrabe into ngspice) can some
> one give me advice of what it is needed, so I can help ?
> 
> 
> Thank you,
> Paolo
>  
-- 
Stefan Jones <ste...@mu...>
Multigig Ltd