On Wed, 2006-10-18 at 20:11 -0400, Stuart Brorson wrote: > Unfortunately, gsch2pcb has the footprint search paths hardcoded into > the code along with a project RC file. Pcb uses its own, different > config files. Therefore, bad things can happen.
Are these in $PREFIX/share/gEDA/scheme/gnet-gsch2pcb.scm Mine has: (define m4-command "/usr/bin/m4") (define m4-pcbdir "/home/pcjc2/geda/share/pcb/m4") (define m4-pcbconfdir "/home/pcjc2/geda/etc/pcb") (define m4-files "") Perhaps a temporary solution / workaround is to edit this file. I don't see any references to newlib in there, so perhaps that is hardcoded in the source (I haven't looked). I do recall it being mentioned that newlib does pass through M4 at some stage, just no macros get expanded. Perhaps that is just PCB internal footprint instanciation though. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
