File: lepton-sch2pcb.1

package info (click to toggle)
lepton-eda 1.9.18-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 41,024 kB
  • sloc: ansic: 66,688; lisp: 29,508; sh: 6,792; makefile: 3,111; perl: 1,404; pascal: 1,161; lex: 887; sed: 16; cpp: 8
file content (166 lines) | stat: -rw-r--r-- 6,164 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
.TH lepton-sch2pcb 1 "May 29, 2022" "Lepton EDA" 1.9.18.20220529
.SH NAME
lepton-sch2pcb - Update PCB layouts from Lepton EDA schematics
.SH SYNOPSIS
\fBlepton-sch2pcb\fR [\fIOPTION\fR ...] {\fIPROJECT\fR | \fIFILE\fR ...}
.SH DESCRIPTION
.PP
\fBlepton-sch2pcb\fR is a frontend to \fBlepton-netlist\fR(1) which aids in
creating and updating \fBpcb\fR(1) printed circuit board layouts based
on a set of electronic schematics created with \fBlepton-schematic\fR(1).

.PP
Instead of specifying all options and input schematic \fIFILE\fRs
on the command line, \fBlepton-sch2pcb\fR can use a \fIPROJECT\fR file
instead.

.PP
\fBlepton-sch2pcb\fR first runs \fBlepton-netlist\fR(1) with the `PCB' backend (or
backend specified by --backend-net) to create a `<name>.net' file
containing a \fBpcb\fR(1) formatted netlist for the design.

.PP
The second step is to run \fBlepton-netlist\fR(1) again with the `gsch2pcb'
backend (or backend specified by --backend-pcb) to find any \fBM4\fR(1)
elements required by the schematics.
Any missing elements are found by searching a set of file element
directories.  If no `<name>.pcb' file exists for the design yet, it is
created with the required elements; otherwise, any new elements
are output to a `<name>.new.pcb' file.

.PP
If a `<name>.pcb' file exists, it is searched for elements with a
non-empty element name with no matching schematic symbol.  These
elements are removed from the `<name>.pcb' file, with a backup in a
`<name>.pcb.bak' file.

.PP
Finally, \fBlepton-netlist\fR(1) is run a third time with the `pcbpins'
backend (or backend specified by --backend-cmd) to create a
`<name>.cmd' file.  This can be loaded into \fBpcb\fR(1) to rename
all pin names in the PCB layout to match the schematic.

.SH OPTIONS
.TP 8
\fB-o\fR, \fB--output-name\fR=\fIBASENAME\fR
Use output filenames `\fIBASENAME\fR.net', `\fIBASENAME\fR.pcb', and
`\fIBASENAME\fR.new.pcb'.  By default, the basename of the first
schematic file in the list of input files is used.
.TP 8
\fB-d\fR, \fB--elements-dir\fR=\fIDIRECTORY\fR
Add \fIDIRECTORY\fR to the list of directories to search for PCB file
elements.  By default, the following directories are searched if they
exist: `./packages', `/usr/local/share/pcb/newlib',
`/usr/share/pcb/newlib', `/usr/local/lib/pcb_lib', `/usr/lib/pcb_lib',
`/usr/local/pcb_lib'.
.TP 8
\fB-f\fR, \fB--use-files\fR
Force use of file elements in preference to elements generated with
\fBM4\fR(1).
.TP 8
\fB-s\fR, \fB--skip-m4\fR
Disable element generation using \fBM4\fR(1) entirely.
.TP 8
\fB--m4-file\fR \fIFILE\fR
Use the \fBM4\fR(1) file \fIFILE\fR in addition to the default M4
files `./pcb.inc' and `~/.pcb/pcb.inc'.
.TP 8
\fB--m4-pcbdir\fR \fIDIRECTORY\fR
Set \fIDIRECTORY\fR as the directory where \fBlepton-sch2pcb\fR should look
for \fBM4\fR(1) files installed by \fBpcb\fR(1).
.TP 8
\fB-r\fR, \fB--remove-unfound\fR
Don't include references to unfound elements in the generated `.pcb'
files.  Use if you want \fBpcb\fR(1) to be able to load the
(incomplete) `.pcb' file.  This is enabled by default.
.TP 8
\fB-k\fR, \fB--keep-unfound\fR
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 \fBpcb\fR(1).
.TP 8
\fB-p\fR, \fB--preserve\fR
Preserve elements in PCB files which are not found in the schematics.
Since elements with an empty element name (schematic "refdes") are
never deleted, this option is rarely useful.
.TP 8
\fB--backend-cmd\fR \fIBACKEND\fR
Use \fIBACKEND\fR to generate `<name>.cmd' file instead of
the default one (`pcbpins').
.TP 8
\fB--backend-net\fR \fIBACKEND\fR
Use \fIBACKEND\fR to generate `<name>.net' file instead of
the default one (`PCB').
.TP 8
\fB--backend-pcb\fR \fIBACKEND\fR
Use \fIBACKEND\fR to generate `<name>.pcb' file instead of
the default one (`gsch2pcb').
.TP 8
\fB--gnetlist\fR \fIBACKEND\fR
In addition to the default backends, run \fBlepton-netlist\fR(1) with `\-g
\fIBACKEND\fR', with output to `<name>.\fIBACKEND\fR'.
.TP 8
\fB--gnetlist-arg\fR \fIARG\fR
Pass \fIARG\fR as an additional argument to \fBlepton-netlist\fR(1).
.TP 8
\fB--empty-footprint\fR \fINAME\fR
If \fINAME\fR is not `none', \fBlepton-sch2pcb\fR will not add elements for
components with that name to the PCB file.  Note that if the omitted
components have net connections, they will still appear in the netlist
and \fBpcb\fR(1) will warn that they are missing.
.TP 8
\fB--fix-elements\fR
If a schematic component's `footprint' attribute is not equal to the
`Description' of the corresponding PCB element, update the
`Description' instead of replacing the element.
.TP 8
\fB-q\fR, \fB--quiet\fR
Don't output information on steps to take after running \fBlepton-sch2pcb\fR.
.TP 8
\fB-v\fR, \fB--verbose\fR
Output extra debugging information.  This option can be specified
twice (`\-v \-v') to obtain additional debugging for file elements.
.TP 8
\fB-h\fR, \fB--help\fR
Print a help message.
.TP 8
\fB-V\fR, \fB--version\fR
Print \fBlepton-sch2pcb\fR version information.

.SH PROJECT FILES
.PP
A \fBlepton-sch2pcb\fR project file is a file (not ending in `.sch')
containing a list of schematics to process and some options.  Any
long-form command line option can appear in the project file with the
leading `\-\-' removed, with the exception of `\-\-gnetlist-arg',
`\-\-fix-elements', `\-\-verbose', and `\-\-version'.  Schematics should be
listed on a line beginning with `schematics'.
.PP
An example project file might look like:

.nf
	schematics partA.sch partB.sch
	output-name design
.ad b

.SH ENVIRONMENT
.TP 8
.B NETLISTER
specifies the \fBnetlister\fR(1) program to run.  The default is
`lepton-netlist'.

.SH AUTHOR
Bill Wilson

.SH COPYRIGHT
.nf
Copyright \(co 2012-2017 gEDA Contributors.
Copyright \(co 2017-2022 Lepton Developers.
License GPLv2+: GNU GPL version 2 or later. Please see the `COPYING'
file included with this program for full details.
.PP
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

.SH SEE ALSO
\fBlepton-schematic\fR(1), \fBlepton-netlist\fR(1), \fBpcb\fR(1)