[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-user: RE: gsch2pcb hangs with long footprint names (was: nothing)
- To: geda-user@xxxxxxxx
- Subject: gEDA-user: RE: gsch2pcb hangs with long footprint names (was: nothing)
- From: James Cotton <peabody124@xxxxxxxxx>
- Date: Tue, 13 Dec 2005 17:52:56 -0600
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Tue, 13 Dec 2005 18:52:58 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BNV3Bp4CXAZCg3ThNa2/rAWETqt0xyMeXLqW3DNVWMN44BG85YE5q3DVyMpKzSclYo0Y3wqqU6Edm4BkNAcvgVcgLjJd0TVrHCvGalgXRMC45MB+3ZCNS5grpMnRp/8g2JWPBgPlh97o53e4G7jXCOdsQQxBltWHzh/DLqXCRYU=
- Reply-to: geda-user@xxxxxxxx
- Sender: owner-geda-user@xxxxxxxx
I came across a quirk that I thought I'd let people know about.
Thanks go to John Luciani for helping me figure this one out.
I was using the IPC standard for footprints, and noticed that when I
added footprint=LED-200L-150W my LED's, or
footprint=TSSOP-50P-800L-10N to other parts gsch2pcb would crap out on
me. I was running gsch2pcb with the -f (force newlib) and -d (path to
newlib) options. John suggested that it might be a conflict with the
m4 library, so I set that to (define m4-pcbdir "") in gnet-sch2pcb.
However gsch2pcb overrode the path to /usr/share/pcb/m4. I ended up
fixing this by moving that directory and creating an empty one, which
actually fixed the hang. Anyway, this doesn't really seem like
expected behavior.
Have a good one,
James
When I ran sch2pcb it said:
*********************************************************************
Loading schematic
[/home/jcotton/documents/geda/msp430-cc2420/msp430-cc2420.sch]Default
m4-pcbdir: /usr/share/pcb/m4
--------
gnet-gsch2pcb-tmp.scm override file:
(define m4-pcbdir "/usr/share/pcb/m4")
--------
Running command:
gnetlist -g gsch2pcb -o msp430-cc2420.new.pcb -m
gnet-gsch2pcb-tmp.scm msp430-cc2420.sch
***********************************************************************
I grep'd the geda source and found that the gsch2pcb.c file hard codes
this path in there. On and deleting that gnet-gsch2pcb-tmp.scm just
causes it to get recreated.