X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Mon, 31 Jul 2017 04:05:27 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] pinmapper filter
In-Reply-To:	<xnzibl5qg5.fsf@envy.delorie.com>
Message-ID:	<alpine.DEB.2.00.1707310359520.27212@igor2priv>
References:	<xnzibl5qg5 DOT fsf AT envy DOT delorie DOT com>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 30 Jul 2017, DJ Delorie wrote:

>
> My original design was like that, but in this case I have three related
> things:
>
> 1. The footprint
> 2. The pin mapping
> 3. The vendor/manufacturer information (attributes)
>
> I really don't want these things separated.  I also found, while using
> it, that was easy to just edit the mapping in emacs and hit "import" in
> pcb.

On the higher level (devmap) it's not separated in my design either. A 
file called bss84_sot23 contains:

attr footprint=SOT23
attr lomex=86-03-04
attr pinmap=G=1
attr pinmap=S=2
attr pinmap=D=3

(An attr line is nothing more than just tellnig devmap toedit the 
attribute of the affected symbol while it's being processed.)

Then I just add "devmap=bss84_sot23" in gschem instead of the 
footprint=attribute. Devmap then edits all attributes the above file says, 
including footprint and pinmap and then the low level pinmapper executes 
the pin renumbering using the pinmap atribute.

The only separation is that I also have direct access to the low level, so 
if I don't want to add a devmap file in the  database, I can just add a 
pinmap attribute in gschem, "embedding" the pinout into a heavy symbol.

- Raw text -