[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnucap-devel] git repo proposal
From: |
Felix Salfelder |
Subject: |
Re: [Gnucap-devel] git repo proposal |
Date: |
Mon, 27 May 2013 08:55:33 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Mon, May 27, 2013 at 02:32:57AM -0400, al davis wrote:
> On Monday 27 May 2013, Felix Salfelder wrote:
> > lets
> > draw a clear line between user and developer.
>
> The line isn't so clear. A "user" could be using Verilog-AMS as
> a simulation language. The behavioral models need to be
> compiled. So, "users" are making plugins.
> A "developer" may be using gnucap to develop a model for
> distribution, but often the target will not be gnucap.
okay, lets start.
installing gnucap (apt-get, yum) is on the user/administator side
installing from source
tar -x
./configure; make install
is on the power-user/distributor side
using git
git clone ...
cd gnucap; (autogen or not) ./configure(.old or not)
make install
is on the developer side
.load foo.{vams,cc,cpp,...}
is on the user side.
developping packages other than gnucap is on the developer side.
(i'm sure this is incomplete.)
felix
- Re: [Gnucap-devel] git repo proposal, (continued)
Re: [Gnucap-devel] git repo proposal, Felix Salfelder, 2013/05/26