| 
      
      
      From: <sd...@cl...> - 2003-07-08 12:10:26
      
     | 
| Hi -- > 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 ? The thing you need from Spice-OPUS is the cmpp compiler. It is used to turn the .mod and .ifs files into .c files. It is also used when making the codemodel .cm (shared-object) files. It is not a part of the tclspice code; rather, it is a compiler used to build the code. > Georgia Tech now have set a download page for xspice code. What's the URL? Does the stuff work? The XSpice stuff in ngspice was originally non-functional. > Has the original GTRI package the necessary functions that will free us > from the Spice-OPUS dependence ? According to his e-mail of a couple weeks ago, Stefan has fixed the GTRI cmpp & placed it in the CVS. > 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 ? If I were you, I would try to keep all the changes I incorporated int tclspice-0.2.10-sdb. Not only is the XSpice stuff POLY stuff working now, but I also made a lot of changes to the src/frontend/parser in order to handle complicated netnames & handle embedded vendor .subckts. You can get my code from: http://www.brorson.com/gEDA/ngspice/ngspice.html As Stefan said, do a diff -ru against your stuff to see what is different. Stuart > > > Thank you, > Paolo > > > -- > -- > Paolo Nenzi > GnuPG public key available on keyservers > Key FingerPrint: FCC5 FDA4 4A31 EDE6 982D AABE 6D48 9D3A 8FC0 A981 > > |