Mail Archives: geda-user/2013/12/13/16:04:03
Rob,
I've never trusted the ".." construct in gafrc for the simple reason
that it didn't seem to work. I've always used something like this:
(component-library "${HOME}/gaf/local-sym/misc")
This always seems to work. I haven't tried it, but according to the
DOCS, you should also be able to define a symbol in gafrc like this:
(define mysym "${HOME}/gaf/local-sym")
and then reference libs like this:
(component-library (build-path mysym "misc"))
Regarding the giant symbol problem, as long as you are using the
standard 0.1 spacing, 100 pins will be a bit big. What I've done in the
past is to break up the symbol into parts - something like PICXX_PortA,
PICXX_PortB, etc. Each having only 8 pins. As long as you get the pin
numbering right and give each component the same ID (eg. IC12) and the
same footprint, the netlister will drop them all into the same package.
Many times this also makes the schematic a lot simpler too.
Steve Besch
On 12/13/2013 03:33 PM, Rob Butts wrote:
> As it happens I do have a /home/rob/.gEDA directory. I had to show
> hidden files. I put a gafrc file in there and then opened a schematic
> in a project folder in the gaf folder. It did not show a symbols
> sub-folder that I defined in the gafrc file as:
> (component-library "../gschem-sym/Microchip")
>
--
fictio cedit veritati
- Raw text -