Re: gEDA-user: Where do I put footprints?

2010-02-10 Thread DJ Delorie
> > lib-newlib = /envy/dj/geda/gedasymbols/www/user/dj_delorie/footprints:. : separates items in the list. > with . added, any subdirs will be searched for footprints? With "." added, any ./* subdirectory is searched for footprints. ___ geda-user ma

Re: gEDA-user: Where do I put footprints?

2010-02-10 Thread Jim
John Griessen wrote: DJ Delorie wrote: I use the new pcb-import code, so I have pcb's footprint path set up to include an absolute path for the global tree, and "." I.e. ~/.pcb/settings has this line: lib-newlib = /envy/dj/geda/gedasymbols/www/user/dj_delorie/footprints:. So, that : is the s

Re: gEDA-user: Where do I put footprints?

2010-02-10 Thread John Griessen
DJ Delorie wrote: I use the new pcb-import code, so I have pcb's footprint path set up to include an absolute path for the global tree, and "." I.e. ~/.pcb/settings has this line: lib-newlib = /envy/dj/geda/gedasymbols/www/user/dj_delorie/footprints:. So, that : is the syntax for adding direc

Re: gEDA-user: Where do I put footprints?

2010-02-10 Thread DJ Delorie
I have a personal-global footprint tree (happens to be a copy of my gedasymbols area) that every project points to. In addition, every project has a ./footprints subdir with project-specific footprints in it. I use the new pcb-import code, so I have pcb's footprint path set up to include an abso

Re: gEDA-user: Where do I put footprints?

2010-02-10 Thread John Griessen
Jim wrote: I know this seems like a trivial question but I've googled for hours trying to find 1. What goes into gafrc other than component-library? Lines like: (source-library "../tmote-revb_") for your local symbols, if any. (There are always some! Mine are about 95% local versions)

gEDA-user: Where do I put footprints?

2010-02-10 Thread Jim
I know this seems like a trivial question but I've googled for hours trying to find 1. What goes into gafrc other than component-library? 2. Where do I put my locally generated footprints? I tried putting them in the component-library, the same file with the schematic et al. Out of desparati