The current arrangement for `automaking' monoliths appears to expect
for each task a .f and and .ifl for each task. In the case of
traditional Figaro there are interface files without separate named
tasks, e.g. ELSPLOT is a variant of LSPLOT; and there is Fortran source
which has no corresponding interface, because the Fortran is used for a
number of tasks, e.g. figaro1/grow3.f for GROWXY, GROWXT, and GROWYT.
Now I can think of some kludges, but I thought I'd ask what the
recommended automake approach was in such cases.
Malcolm
|