On Wed, 2009-01-07 at 13:59 +0200, Duncan Drennan wrote: > I just picked up a bug with gsch2pcb with the output path specification. > > If I run the command > > gsch2pcb -v -d d:\Projects\footprints\trunk --skip-m4 -o > ../../pcb/trunk/node node.sch > > then everything goes well and works nicely. If I run > > gsch2pcb -v -d d:\Projects\footprints\trunk --skip-m4 -o > ..\..\pcb\trunk\node node.sch
> it fails. It appears as if something (possibly gnetlist) has an issue > with the backslash instead of the forward slash. Here is the complete > output from the failed command: Can you make a backup and run the following gnetlist command: [snip] > Loading schematic [d:\Projects\xxxxx\schematics\trunk\node.sch] > Skipping the m4 processor for pcb footprints > -------- > gsch2pcb: gnetlist command (gnetlist -g gsch2pcb -o > ..\..\pcb\trunk\node.new.pcb > -m gnet-gsch2pcb-tmp.scm node.sch) failed. > At least gnetlist 20030901 is required for m4-xxx options. gnetlist -g gsch2pcb -o ..\..\pcb\trunk\node.new.pcb -m gnet-gsch2pcb-tmp.scm node.sch (Making sure gnet-gsch2pcb-tmp.scm exists, and has the contents you pasted in the original email). What is the specific console output of that command? Can you post the gnetlist.log file produced when running it. Best wishes, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
