FreeCalypso > hg > ueda-linux
comparison ueda/man/ueda-getfps.1 @ 0:cd92449fdb51
initial import of ueda and ifctf-part-lib from ifctfvax CVS
author | Space Falcon <falcon@ivan.Harhan.ORG> |
---|---|
date | Mon, 20 Jul 2015 00:24:37 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:cd92449fdb51 |
---|---|
1 .TH GETFPS 1 "" "International Free Computing Task Force" \ | |
2 "uEDA Suite Documentation" | |
3 .SH NAME | |
4 ueda-getfps \- fetch all footprints for the board | |
5 .SH SYNOPSIS | |
6 .B ueda-getfps | |
7 [ | |
8 .B \-c | |
9 ] [ | |
10 .B \-h | |
11 ] | |
12 .B | | |
13 .B ueda-runm4 | |
14 .SH DESCRIPTION | |
15 .PP | |
16 .I Ueda-getfps | |
17 reads the MCL, extracts all | |
18 .B footprint= | |
19 attributes and generates a set of | |
20 .IR m4 (1) | |
21 macro calls which then needs to be run through | |
22 .IR ueda-runm4 (1). | |
23 The complete | |
24 .B | |
25 ueda-getfps | ueda-runm4 | |
26 pipeline produces the complete set of PCB elements (footprints) for the board. | |
27 .PP | |
28 The | |
29 .B \-c | |
30 option instructs | |
31 .I ueda-getfps | |
32 to check the design for the completeness of the pre-layout information. | |
33 Normally components in the MCL which do not have a | |
34 .B footprint= | |
35 attribute or have it set to | |
36 .B TBD | |
37 are ignored, but the | |
38 .B \-c | |
39 option causes a warning message to be issued instead. | |
40 .PP | |
41 The | |
42 .B \-h | |
43 option causes | |
44 a blank PCB template to be prepended as a header before the PCB elements | |
45 so that the resulting pipeline output is a complete and valid PCB layout file. | |
46 .SH FILES | |
47 MCL Master Component List | |
48 .SH SEE ALSO | |
49 ueda-cutelements(1), ueda-instfileelem(1), ueda-runm4(1) | |
50 .br | |
51 Introductory uEDA documentation | |
52 .SH DIAGNOSTICS | |
53 /usr/local/eda/ifctf-part-lib/m4-fp: bad directory | |
54 .in +8 | |
55 The required IFCTF part library is not installed correctly. | |
56 .in -8 | |
57 /usr/local/eda/file-element-dirs: No such file or directory | |
58 .in +8 | |
59 If a requested footprint is not found in the M4 library, the M4 code | |
60 automatically invokes | |
61 .IR ueda-instfileelem (1) | |
62 to look for it in the file element directories. | |
63 If the latter are not installed, you see this rather cryptic error message. | |
64 .in -8 | |
65 No footprint named \fIxxx\fP | |
66 .in +8 | |
67 The requested footprint could not be found, neither in M4 nor in the file | |
68 element libraries. | |
69 .in -8 | |
70 \fIXX\fP has no footprint | |
71 .br | |
72 \fIXX\fP: footprint=TBD | |
73 .in +8 | |
74 These diagnostics are produced with the | |
75 .B \-c | |
76 option and should be self-explanatory. | |
77 .in -8 | |
78 .SH BUGS | |
79 Exposing the | |
80 .IR ueda-getfps | ueda-runm4 | |
81 pipeline to the user is ugly. |