gsch2pcb 1.6

usage: gsch2pcb [options] {project | foo.sch [foo1.sch ...]} Generate a PCB layout file from a set of gschem schematics. gnetlist -g PCB is run to generate foo.net from the schematics. gnetlist -g gsch2pcb is run to get PCB m4 derived elements which match schematic footprints. For schematic footprints which don't match any PCB m4 layout elements, search a set of file element directories in an attempt to find matching PCB file elements. Output to foo.pcb if it doesn't exist. If there is a current foo.pcb, output only new elements to foo.new.pcb. If any elements with a non-empty element name in the current foo.pcb have no matching schematic component, then remove those elements from foo.pcb and rename foo.pcb to a foo.pcb.bak sequence. gnetlist -g pcbpins is run to get a PCB actions file which will rename all of the pins in a .pcb file to match pin names from the schematic. "project" is a file (not ending in .sch) containing a list of schematics to process and some options. A schematics line is like: schematics foo1.sch foo2.sch ... Options in a project file are like command line args without the "-": output-name myproject options (may be included in a project file): -d, --elements-dir D Search D for PCB file elements. These defaults are searched if they exist: ./packages, /usr/local/share/pcb/newlib, /usr/share/pcb/newlib, (old pcb) /usr/local/lib/pcb_lib, /usr/lib/pcb_lib, (old pcb) /usr/local/pcb_lib -o, --output-name N Use output file names N.net, N.pcb, and N.new.pcb instead of foo.net, ... where foo is the basename of the first command line .sch file. -f, --use-files Force using file elements over m4 PCB elements for new footprints even though m4 elements are searched for first and may have been found. -r, --remove-unfound Don't include references to unfound elements in the generated .pcb files. Use if you want PCB to be able to load the (incomplete) .pcb file. This is the default behavior. -k, --keep-unfound Keep include references to unfound elements in the generated .pcb files. Use if you want to hand edit or otherwise preprocess the generated .pcb file before running pcb. -p, --preserve Preserve elements in PCB files which are not found in the schematics. Note that elements with an empty element name (schematic refdes) are never deleted, so you really shouldn't need this option. -q, --quiet Don't tell the user what to do next after running gsch2pcb. -s, --skip-m4 Skip m4 when looking for footprints. The default is to use m4 (which is what previous versions did). --m4-file F.inc Use m4 file F.inc in addition to the default m4 files ./pcb.inc and ~/.pcb/pcb.inc. --m4-pcbdir D Use D as the PCB m4 files install directory instead of the default: /usr/share/pcb/pcb/m4 --gnetlist backend A convenience run of extra gnetlist -g commands. Example: gnetlist partslist3 Creates: myproject.partslist3 --empty-footprint name See the project.sample file. options (not recognized in a project file): --gnetlist-arg arg Allows additional arguments to be passed to gnetlist. --fix-elements If a schematic component footprint is not equal to its PCB element Description, update the Description instead of replacing the element. Do this the first time gsch2pcb is used with PCB files originally created with gschem2pcb. -v, --verbose Use -v -v for additional file element debugging. -V, --version environment variables: GNETLIST If set, this specifies the name of the gnetlist program to execute. Additional Resources: gnetlist user guide: http://geda.seul.org/wiki/geda:gnetlist_ug gEDA homepage: http://www.gpleda.org PCB homepage: http://pcb.gpleda.org