© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Thanks Mitch.
Point 1 is sort of iffy. In general, it would be nice to support spaces in filenames. Whether we like it or not, the computing world is moving in a direction where it is expected that you can do this.
Point 2 is the real problem here, that gsch2pcb doesn't produce the correct output as a result of there being a space in the footprint filename. The bug is in the gsch2pcb.scm gnetlist backend... written in scheme... Maybe I can get one of the gschem/gnetlist developers to fix this.
Point 3 is a bug in pcb, that pcb provides no explanation as to why it failed to load the file. Unfortunately, this may be a difficult bug to fix as our parser is not easy to work with. I'll have to dig into this at some point, but it's going to take a fair bit of time to work out.
Possible workarounds:
1. Forego putting the footprint into gschem, and then add the footprint manually in pcb using File > Load element data to paste-buffer and then renaming the element with the correct refdes.
2. Create a copy of the offending footprint files, rename them without spaces, label the parts with those footprint names in gschem, and then point gsch2pcb at your local footprint library with the renamed parts.