[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gEDA: gschem2pcb question



Ales Hvezda wrote:
> 
> Chris,
> 
> [snip]
> >The weird part is that U1 gets processed correctly, so gaf knows what
> >"SMD" is, then when U2 comes around, it doesn't know it anymore ...
> 
>         Actually U1 is also not correct, because the footprint in it
> is "D 8" which I don't think is a valid PCB name.  The reason all this
> is failing is because of the spaces in the value of the footprint
> attribute (ie SMD 14).  What's the solution to this?  Are spaces in
> footprints valid for PCB?  Anybody run across this before?
> (btw, I think it's the spaces causing the problems, but I could be wrong).
> 

Now I'm confused. The footprint for U1 is correctly processed. I know
because I have a PCB on my bench right now with 4 MC100ELT23-1.sym parts
on it and it works ...
I double checked that part and it has footprint=SMD 8 so I don't know
where you got that "D 8" from ...

Also I've never had problem before with attaching footprint=DIL 14 300
to a component on the schematics.

spaces are definitely allowed, since that's how you send commands and
arguments to the m4 macros.
It goes like this: footprint= your_footprint $arg1 $arg2 $arg3 $arg4 ...

where $arg1 is usually x dimension, $arg2 is y dimension, or $arg1 is
nbr of pins and $arg2 is width, or $arg1 is a radius, ...

The plot thickens ....

Chris.