1gschem(1) 1.6.2.20110115 gschem(1)
2
6 gschem - gEDA/gaf Schematic Capture
7
9 gschem [-q] [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output‐
10 filename] [-p] [-h] [schematic1 ... schematicN]
11
13 gschem is the schematic capture program which is part gEDA (GPL Elec‐
14 tronic Design Automation) toolset. This program is used to draw elec‐
15 tronic schematics. Schematics consist of standard symbols (which are
16 either part of a standard library or created by the user) which repre‐
17 sent the various gates and components. These components are then
18 interconnected by nets (wires). Schematics may be printed to a Post‐
19 Script file for printing or further conversion to other output formats.
20 Output to various image formats is also supported.
21 gschem is also the symbol creation editor. All the standard methods of
23 creating schematics are used in the creation of symbols. There are a
24 few special rules when creating symbols, so please refer to the (non-
25 existant as of now) symbol creation document.
26 Please read the official documentation (very minimal at this point) on
28 how to use gschem, since this man page just describes the command line
29 arguments and a few examples on how to run gschem.
30
33 gschem accepts the following options:
34 -q Quiet mode on. This mode turns off all warnings/notes/mes‐
36 sages. (optional)
37 -v Verbose mode on. This mode gives as much feedback to the user
39 as possible. (optional)
40 -t Print out more information when using mouse strokes. With this
42 command line flag and the middle button configured for mouse
43 strokes, gschem will output the stroke sequence numbers as the
44 user executes strokes. These numbers can be used to define new
45 strokes in the system-gschemrc file.
46 -r filename
48 Specify a rc filename. Normally gschem searches for the sys‐
49 tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
50 in the current directory. This options allows the user to
51 specify an additional rc file which is read after all the other
52 rc files are read. (optional)
53 -s filename
55 Specify a guile script to be executed at startup. (optional)
56 -o filename
58 Specify a filename for postscript output. This command line
59 argument is useful when running gschem from a shell script and
60 with a guile script. The filename can be changed through the
61 print dialog box.
62 -p Automatically place the window, especially useful if running
64 gschem from the command line and generating output.
65 -h Print out short command line help.
67 schematic1 [... schematicN]
69 Schematic file to be loaded. Specifing a schematic file is
70 optional. If multiple schematic files are specified they are
71 read in sequentially and put on seperate pages. It is impor‐
72 tant that the schematic(s) follow all the options (ie last).
73
76 These examples assume that you have a schematic called stack_1.sch in
77 the current directory
78 To run gschem and then interact with the program:
80 gschem
82 To run gschem in interactive mode but load a sample schematic:
84 gschem adders_1.sch
86 To run gschem and load up all schematics in the current subdirectory:
88 gschem *.sch
90
93 gschem respects the following environment variable:
94 GEDADATA
96 specifies where the various required scheme and rc files are
97 located (the default is ${prefix}/share/gEDA). This environ‐
98 ment variables does not need to be set by the end user unless
99 they are moving the executables to a new install ${prefix}.
100
103 Ales Hvezda and many others
104
107 gnetlist(1), gsymcheck(1)
108
110 Copyright © 1999-2008 Ales Hvezda
111 This document can be freely redistributed according to the terms of the
113 GNU General Public License version 2.0
114Version January 15th, 2011 gschem(1)