Ticket #154 (Fixed)Fri Nov 02 03:05:38 UTC 2007

Parsing problem for !Depend interface files.

Details by Steve Revill (20):

Reported by Rob F Johnson:

I have been using the GCC C compiler on the RISC OS components
released by ROOL. I have been trying to integrate the GCC compiler
into the !Builder system of Makefiles.

GCC provide a compiler parameter -mamu to output dependencies for amu
to pick up and incorporate as Dynamic Dependencies in the Makefile. I
have found that amu doesn’t like the GCC output format when there are
more than a few dependencies for any one object.

My first attachment shows a typical -mamu output (from the Edit source
file edit). The second attachment shows what amu convers this to in
the Dynamic Dependency section of the makefile. A later pass of amu
then objected to the obviously invalid result.

My first comment is that GCC’s output is a valid format for
dependencies. If amu had copied it as is, all would be well.

amu prefers to convert the multiple dependencies of o.edit to single
dependencies each on its own line (the format that your own compiler
outputs anyway). It is obviously quite happy with the concept of the
multiple dependency input. But it doesn’t interpret the continuation
indicator \ correctly.

Your documentation of Makefile syntax in the Desktop Tools manual says
that \ can be used as a continuation indicator on any type of line,
including dependencies. There is no specific definition of the format
of the !Depend interface file, but it is reasonable to expect that any
valid dependency format would be acceptable.

The fact that amu obviously expects the possibility of multiple
dependent files on one line suggests that it is only an error that
continuation lines are not catered for. The only other alternatives
are that it expects a different continuation indicator, or that it can
handle a line of any length without needing it to be split.

I am using a recent (this year) copy of the C/C++ System, with !AMU v
5.27, on an OS 4.02 StrongArm RiscPC.