Re: gEDA-user: pcb: experience with import-schematics

[DJ Delorie <dj@xxxxxxxxxxx>]

> >> More generally: What config files does import schematics look at?
> > Importing uses pcb's internal paths, not gafrc.
> 
> This adds to the confusion.

No, this is the same confusion that's always existed, which is why we
wanted to get rid of gsch2pcb and *only* use pcb's list.  We've always
had the problem of gsch2pcb and pcb's library not having the same list
of parts, or not searching the same locations, etc.

> From a user point of view I don't care which of the two applications is the 
> master of the footprint path. But there definitely should be just one unique 
> config for gnetlist and pcb import.

It's not gnetlist, it's gsch2pcb.  gnetlist knows *nothing* of pcb's
libraries.  gsch2pcb knows way too much about pcb's internals.

> If the pcb internal path variable is the way to go, it should be possible to 
> set it differently for different projects.

It can go in a local pcb.settings file.  I don't think the *.pcb
should have it, because the location is machine-dependent, not
board-dependent.

> > You can point pcb's m4 library at a non-existing directory, I suppose.
> 
> Unfortunately, if the m4 library can't be disabled, or at least be 
> considered as lowest priority, the import feature is no much use for me. 
> I'd suggest a m4 enable switch in the library 

That's what pointing the library query program at /bin/true does.

> > Maybe we need to read the menus in reverse order?
>                             ^^^^^
>                             paths?

No, read the code and it will make sense.  :-P

> I'd say, the last path should receive highest priority. This is how the PATH 
> environment variable of the shell is parsed. 

$PATH is the other way - first match wins, not last match.


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user