Stuart Brorson wrote:
I'm looking for some help in debugging this problem. Is there an
intermediate step I can run to try and figure out if the problem is
with the footprint or my schematic? What triggers the m4 library to
kick in?
I see a long discussion thread about your particular problem, so I
won't interfere there. However, to see what libraries are searched
for footprints, you can run gsch2pcb in double verbose mode:
gsch2pcb -v -v project
It will print out a detailed itinery of what it is doing while
processing your board. THis is very useful for debug purposes like
the one you have at hand.
Stuart
_______________________________________________
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Thanks for contributing. I've been trying do debug this problem for
quite some time and as a newbie it been quite challenging to figure this
one out. Familiar with some common command line switches I looked for
the -v option a couple of weeks ago and found it be helpful. I also
found the comments about checking for schematic errors using gnetlist -g
... to be helpful as well. The frustrating thing is that the error
information is the same. I tried the double -v switch on the test.sch
we created to try and figure out this problem and didn't seem to give me
any more clues.
Jeff
_______________________________________________
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user