[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: gedasymbols.org update

To: geda-user@xxxxxxxx
Subject: Re: gEDA-user: gedasymbols.org update
From: John Doty <jpd@xxxxxxxxxxxxx>
Date: Mon, 6 Mar 2006 07:08:40 +0900
Delivered-to: archiver@seul.org
Delivered-to: geda-user-outgoing@seul.org
Delivered-to: geda-user@seul.org
Delivery-date: Sun, 05 Mar 2006 17:09:00 -0500
In-reply-to: <200603051348.50158.dw@yankee.us.com>
References: <200603040433.k244XjeR020392@envy.delorie.com> <200603051318.42731.dw@yankee.us.com> <200603052123.k25LNkA5009390@envy.delorie.com> <200603051348.50158.dw@yankee.us.com>
Reply-to: geda-user@xxxxxxxx
Sender: owner-geda-user@xxxxxxxx

I have symbols for part of OpenIP (see http://research.kek.jp/people/ ikeda/openIP/). Since a major purpose for these is SPICE netlist generation, they need "file" attributes (but "footprint"? What's that? ;-). But we have no standard way to organize these, and neither SPICE nor spice-sdb have search rules for these.

What I do is place a link to the model library directory (named "Components") in the design directory. Models are in subdirectories of "Components", so, for example, the symbol for the EDFFP block contains "file=Components/OpenIP/openip_3.cir" because the EDFFP model was cribbed from chapter 3 of the OpenIP manual.

Should this be the standard approach? Alternatives?


John Doty              Noqsi Aerospace, Ltd.
jpd@xxxxxxxxxxxxx

References:
- gEDA-user: gedasymbols.org update
  - From: DJ Delorie
- Re: gEDA-user: gedasymbols.org update
  - From: Daniel Wisehart
- Re: gEDA-user: gedasymbols.org update
  - From: DJ Delorie
- Re: gEDA-user: gedasymbols.org update
  - From: Daniel Wisehart

Prev by Author: Re: gEDA-user: Edge ringing filtering
Next by Author: Re: gEDA-user: Edge ringing filtering
Previous by thread: Re: gEDA-user: gedasymbols.org update
Next by thread: Re: gEDA-user: gedasymbols.org update
Index(es):
- Author
- Thread