gEDA-bug: [Bug 897661] Re: --m4-file argument to gsch2pcb does nothing

[Peter TB Brett <897661@xxxxxxxxxxxxxxxxxx>]

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?

** Description changed:

  The '--m4-file FILE' option to gsch2pcb is supposed to "use" the
  specified M4 source FILE when the gsch2pcb backend generates footprints
- using M4.
+ 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 a line which looks like:
+ The generated snippet contains lines that look like:
  
- (define m4-files STRING)
+ (define m4-pcbdir DIRSTRING)
+ (define m4-files FILESTRING)
  
- where STRING is a space-separated list of M4 filenames. However, the
- gsch2pcb gnetlist backend never uses the m4-files variable. This was
+ 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.

** Summary changed:

- --m4-file argument to gsch2pcb does nothing
+ --m4-file and -m4-pcbdir arguments to gsch2pcb do nothing

** Changed in: geda
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/897661

Title:
  --m4-file and -m4-pcbdir arguments to gsch2pcb do nothing

Status in GPL Electronic Design Automation tools:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/897661/+subscriptions


_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug