--m4-file and -m4-pcbdir arguments to gsch2pcb do nothing
Bug #897661 reported by
Peter TB Brett
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gEDA |
Fix Released
|
High
|
Unassigned |
Bug 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. 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.
Changed in geda: | |
milestone: | none → 1.7.2 |
Changed in geda: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Some further investigation indicates that the problem is worse than it initially appeared, and I've updated the bug description accordingly. However, it's obvious that no-one actually uses these options, since they were broken throughout the stable-1.6 series. What about removing them entirely?