hi there.
On Sun, May 26, 2013 at 02:35:35AM -0400, al davis wrote:
> Now that we have the mechanism, I have a few myself .... multi-
> processor support, a modelgen branch with Verilog syntax.
on my end, some things that might be worth importing are
- sensitivity analysis
- dc dynamics analysis
- dc sweep improvements
- lang_spectre patches/fixes
- some parameter scoping issues fixed
- basic unit testing
- lots of experiments involving backend changes
- parameter lists
- ELEMENTs with more than 1 input
- discrete time
- debugging aid
- collapsing node hacks
- probably stuff i don't remember...
i do not really know where to start. would be great if somebody wanted
to help...
> Also, we need to include the plugin tarballs, and set up a way
> for anyone to have a space for their work on plugins.
i have a draft for including plugin package-tarballs into the build
system within the autotools-WIP branch. basically it works like
1) place your package into <gnucap-src>/extern
type
git clone <gitrepo> extern/<name>
cd !$; ./autogen.sh; cd -
or just
tar -xf <tarball> -C extern/<packagename> --strip-components 1
2) run ./configure (once)
3) (todo) make check, install now dives into externals
all we need is one git repo for each plugin-package. i have gitified
gnucap-bsim gnucap-spice3f5 gnucap-geda gnucap-adms and gnucap-bm
(i certainly need some help making all of them work.)
regards
felix
_______________________________________________
Gnucap-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnucap-devel
