X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-CMAE-Analysis:	v=2.4 cv=F76SyotN c=1 sm=1 tr=0 ts=60723d16
	a=+cj0cO56Fp8x7EdhTra87A==:117 a=TfoWMsdAOHEKjG3e1sbudQ==:17
	a=9+rZDBEiDlHhcck0kWbJtElFXBc=:19 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19
	a=IkcTkHD0fZMA:10 a=3YhXtTcJ-WEA:10 a=a1KZgU7cAAAA:8 a=Sf6-h4h4FuMsNGJKKhAA:9
	a=QEXdDO2ut3YA:10 a=ng0hpkU2jXKPaRTLMVYJ:22
X-SECURESERVER-ACCT:	glimrick AT epilitimus DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=epilitimus.com; s=default; h=Content-Transfer-Encoding:Content-Type:
	MIME-Version:Date:Message-ID:Subject:From:To:Sender:Reply-To:Cc:Content-ID:
	Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
	:Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:
	List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=xLUMM3CMK2NxMv6p6jL9RgqI5xU2DUOIW1E02gE8h1U=; b=KX1GrQqIBR6B+b3VH2jlVrWorx
	qFDHDM6rU9fo51hyelKhWqty6Ri/nMLmDWZQ2VdYHM56OiW9cX+wUr+vx6rzWNTHQGBAd7Na4OClX
	qeXFfKAmz/6c7YpK/PIVb6CakAjW24yncKfJkkKAqeNHCw5C7OTOVtXSK7eiONufSacTsPC+Bq8sc
	cOl1Gee49qkxZBaNNXDoCivWScJ6aWp0Ts/HVgxSvoTwRwrPfDpeqH1aFTMIDjZur+lIWtnRPr4pf
	3mRIMxKF5HrykN8IWqRMXliB4AozP/iLh8CaL6OBCDrrFrM9Ugoo9ETVWlQTn6jJxCRqtW5mO2lG9
	yMeWPd7g==;
To:	Roland Lutz <rlutz AT hedmen DOT org>,
	geda-user ailing list <geda-user AT delorie DOT com>
From:	"Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	[geda-user] xspice integration
Message-ID:	<b609b43e-9209-3809-ef0e-d3b1e4b11c3c@epilitimus.com>
Date:	Sat, 10 Apr 2021 16:04:39 -0800
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
	Firefox/60.0 SeaMonkey/2.53.3
MIME-Version:	1.0
X-AntiAbuse:	This header was added to track abuse, please include it with any abuse report
X-AntiAbuse:	Primary Hostname - a2plcpnl0121.prod.iad2.secureserver.net
X-AntiAbuse:	Original Domain - delorie.com
X-AntiAbuse:	Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse:	Sender Address Domain - epilitimus.com
X-Get-Message-Sender-Via:	a2plcpnl0121.prod.iad2.secureserver.net: authenticated_id: glimrick AT epilitimus DOT com
X-Authenticated-Sender:	a2plcpnl0121.prod.iad2.secureserver.net: glimrick AT epilitimus DOT com
X-Source:
X-Source-Args:
X-Source-Dir:
X-CMAE-Envelope:	MS4xfKhea/Co5aAOJiZYZZjHU75EMiCPcOiesnMTOLq7di1o3Bmia0qMuhzOBiEpLRaazVL1+0QYqgQo+S0R6vq4ETfiaTTi3KmaKeP9WiZbWEEi2S/57xcl
	PIuG/j0w8NY3DOWki6kHte8PrfDs816zNq59EIr9qxefoV7RbbnPx/2n690cigj3vO5yHU+8AjCyjyos/00ojP23Izy2qkvmsiXAcfX/y8j36mC9bUtDZYUK
Reply-To:	geda-user AT delorie DOT com

Hi Roland,
Now that the xspice backend is stable I am starting to look at
integrating it into the geda tree. I don't know if you have had a chance
to look at it yet (http://www.epilitimus.com/xspice/). Obviously the
gnet_xspice.py and xpsice_util.py go in xorn/src/backend (as well as
gnet_hierarchy & util_hierarchy, the later is used by gnet_xspice), but
there is more:

symbols:
These go in the symbol tree but I have some thoughts about some tweaks
to that. There are currently symbols directories for cascade, spice with
some gnucap symbols mixed in, and switchcap. To those I am about to add
ones for xspice. My thought was to have a simulation symbols directory
with sub-directories for each of the five simulation packages. There is
some crossover but I think it would make it easier to find what you are
looking for. I have some similar ideas re: other categories but that is
a future discussion.

xpde.py:
This is a stand alone utility except that is does use stuff from
xspice_utll.py (a symlink to the backend version maybe? Or change
sys.path with a relative path before the import?). I think it should be
installed, but then it is only really useful if modifying the device
descriptions, so maybe not. It is definitely needed during the build. As
for where to put it I am thinking since it is a stand alone it belongs
in a sub-directory off the top level. Also maybe just xpde, drop the 'py'?

xml files:
These are used by xpde to generate the python device descriptions at
build time. I am thinking a sub-directory off xpde. The generated python
needs to be installed such that the backend can find them, They are
specific to the backend and gaf knows nothing about them so that seems
like the wrong place for them My inclination is an xspice sub-directory
off the backend install location. If xpde is installed the xml files
probably should as well. Perhaps a configure switch to opt for installation?

lib files:
These could be placed either off the xpde sub-directory or off the
backend directory. They aren't used during the build but need to be
installed. During the build the install location for them is placed into
the xml files before the python is generated. Don't really like the
parallel to rpath but I couldn't come up with a better way to do it
given how ngspice is set up. Anyway as far as install goes they are
platform independent so something like [prefix]/share/xspice seems to
make sense? They are spice libraries, not executables.

dev_schem:
These are for reference or in case someone wants to modify an existing
device so they don't need to be installed. Since they are directly
related to the lib files I would say a sub-directory of wherever those
end up.

test:
Obvious place for this stuff would be examples/xspice.

So currently my thinking is something like:
geda/
-----symbols/
----------simulation/
--------------cascade/
--------------gnucap/
--------------spice/
--------------switchcap/
--------------xspice/
-----xpde/
---------xml/  <---generated python installed to backend/xspice
---------libs/  <---installed to [prefix]/share/xspice
------------dev_schem/
-----xorn/
--------src/
------------backend/
----examples/
--------xspice/

Thoughts?

Glenn

- Raw text -