Mail Archives: geda-user/2024/05/03/07:45:35
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-747931105-1714736589=:2197
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Hi Roger,
On Thu, 2 May 2024, Roger Traylor (traylor AT oregonstate DOT edu) [via
geda-user AT delorie DOT com] wrote:
> Looking at the .sch file that gschlas produces, many components have had
> their refdes removed and now are "refdes=?”. However, invoking gschem on
> the same .sch file, the components have their refdes correctly filled
> in. Bizarre.
this may be my fault. gschlas is one of these tools that exist at the
fringe of the suite and don't get much attention; maybe I broke it without
noticing. (I guess I should make sure all the tools have tests.)
Does embedding the symbols and saving it under a new name in gschem work?
> Am I missing something here? I can’t bear entering all the refdes by
> hand. I am using geda-gaf-1.10.2.
Then you have the xorn infrastructure available, which comes in really
handy here. If embedding the symbols in gschem doesn't work, I can write
a short script for this. (If you want to do so yourself, have a look at
xorn/src/command/convert.py as a starting point. Most of the script is
argument processing; the interesting part starts at "gaf.read.read".)
Roland
--8323329-747931105-1714736589=:2197--
- Raw text -