[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: PCB problems



John beat me to the punch with this piece of advice!   He's right:  By
specifying your search paths, you can control where your footprints
are coming from.  Note that you can also put the search path
directives into a "projectrc" file, like Bill Wilson's tutorial says.

Of course, you probably already know this.

Another point:  I personally avoid the M4 footprints, since I don't
understand them well enough to control them.  YMMV.

Stuart



> 
> You can force  the element paths on the gsch2pcb command line.
> 
>    gsch2pcb --elements-dir ELEMENT_DIR_NAME \
>                     --m4-pcbdir M4_DIR_NAME \
>                     SCH_FILE_NAME
> 
> replacing ELEMENT_DIR_NAME, M4_DIR_NAME and SCH_FILE_NAME with
> the appropriate values.
> 
> I believe the default directories for the symbols are
> INSTALL_DIR/share/pcb/m4 and
> INSTALL_DIR/share/pcb/newlib.
> 
> (* jcl *)
> 
> 
> On 10/23/05, Harold D. Skank <skank54@xxxxxxxxx> wrote:
> > People,
> >
> > I'm running PCB under Red Hat kernel-2.6.9.EL.  The latest kernel update
> > was install within the last week.  The kernel upgrade is the only item I
> > can think of that constitutes any substantial recent change to my
> > system.
> >
> > Previously, I have been running the latest release of PCB, pretty much
> > since the release.  Suddenly, I am picking up a foreign (German,
> > actually, judging from the comments in the Element file) TO126 element.
> > I have run "find" and I cannot locate where the element is coming from!
> > I was able to correct my problem by manually inserting the correct copy
> > of the TO126 element into my pcb file (and that element was in it's
> > usual proper place in the library).  As far as I can tell, only TO126
> > seems to be affected.
> >
> > While the manual correction works for the time being, it doesn't
> > represent a permanent solution.  Any suggestions?
> >
> >         Harold Skank
> >
> >
> 
> 
> --
> http://www.luciani.org
>