| 2011-12-11 09:14:09 |
Peter TB Brett |
description |
The '--m4-file FILE' option to gsch2pcb is supposed to "use" the specified M4 source FILE when the gsch2pcb backend generates footprints using M4.
gsch2pcb generates a snippet of Scheme code which is evaluated by gnetlist between loading the gsch2pcb gnetlist backend and running it. The generated snippet contains a line which looks like:
(define m4-files STRING)
where STRING is a space-separated list of M4 filenames. However, the gsch2pcb gnetlist backend never uses the m4-files variable. This was broken in commit 6d935086d299. |
The '--m4-file FILE' option to gsch2pcb is supposed to "use" the specified M4 source FILE when the gsch2pcb backend generates footprints using M4. The '--m4-pcbdir DIR' option is supposed to set the M4 search path to DIR. Neither do anything at the moment.
gsch2pcb generates a snippet of Scheme code which is evaluated by gnetlist between loading the gsch2pcb gnetlist backend and running it. The generated snippet contains lines that look like:
(define m4-pcbdir DIRSTRING)
(define m4-files FILESTRING)
where FILESTRING is a space-separated list of M4 filenames. However, the gsch2pcb gnetlist backend never uses either of these variables. This was broken in commit 6d935086d299. |
|
