comparison ueda/man/ueda-runm4.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 RUNM4 1 "" "International Free Computing Task Force" \
2 "uEDA Suite Documentation"
3 .SH NAME
4 ueda-runm4 \- run m4 with the PCB footprint library loaded
5 .SH SYNOPSIS
6 .B ueda-runm4
7 .SH DESCRIPTION
8 .PP
9 .I Ueda-runm4
10 is a simple
11 .IR sh (1)
12 script that invokes
13 .IR m4 (1)
14 with all macros of the IFCTF PCB footprint library loaded and available
15 for use.
16 Input may be given on stdin which uses these macros and output will be
17 produced on stdout with all macros correctly expanded.
18 .PP
19 .I Ueda-runm4
20 is normally run as a post-processor for
21 .IR ueda-getfps (1).
22 .SH FILES
23 /usr/local/eda/ifctf-part-lib IFCTF part library
24 .SH SEE ALSO
25 ueda-getfps(1), ueda-instfileelem(1)
26 .br
27 Introductory uEDA documentation
28 .SH DIAGNOSTICS
29 /usr/local/eda/ifctf-part-lib/m4-fp: bad directory
30 .in +8
31 The required IFCTF part library is not installed correctly.
32 .in -8
33 /usr/local/eda/file-element-dirs: No such file or directory
34 .in +8
35 If a requested footprint is not found in the M4 library, the M4 code
36 automatically invokes
37 .IR ueda-instfileelem (1)
38 to look for it in the file element directories.
39 If the latter are not installed, you see this rather cryptic error message.
40 .in -8
41 No footprint named \fIxxx\fP
42 .in +8
43 The requested footprint could not be found, neither in M4 nor in the file
44 element libraries.
45 .in -8
46 .SH BUGS
47 The M4 code in the IFCTF part library uses some features only present
48 in the 4.3BSD-Quasijarus version of
49 .IR m4 (1).