Autoconf/autotools and the Modula-2 language

[Gaius Mulley]

Hi,

I'm trying to add support for Modula-2 in gnu gcc and I'm currently
writing the 'gcc-versionno/libgm2/Makefile.am' for the runtime
libraries. Modula-2 has a number of runtime libraries (pim, iso, min)
and each are built using their own flags. I see with C, C++ that the

libraryname_a_CFLAGS

is honoured when producing the .o from the .c sources. It would be
really useful if the same could be done for Modula-2 when producing
the .o from .mod rules, so for example:

libmin_a_M2FLAGS = -Igm2-libs-min -I$(GM2_SRC)/gm2-libs-min

etc

libpim_a_M2FLAGS = -Igm2-libs -I$(GM2_SRC)/gm2-libs

etc

libiso_a_M2FLAGS = -Igm2-iso -I$(GM2_SRC)/gm2-iso.

My questions fall into two categories:

(i) how much work is it to implement the Modula-2 production
of rules which use M2FLAGS in the same way as C uses CFLAGS?
Also where is a good place to start - the C compiler or
f77?
(ii) would it be possible to produce a m2local.m4 file which my
Makefile.am could include to provide a temporary fix for
Modula-2 support? Or does language support go deeper
than just a few macros? Apologies for my ignorance about
m4 in general.


I see that this was discussed sometime ago for the D language:

https://lists.gnu.org/archive/html/autoconf/2007-10/msg00044.html

which I think in someway might answer (i), but it was a while ago
and I just wanted to check this is still the case,

regards,
Gaius

[Gaius Mulley]

Hi,

ah feel free to ignore my previous email - as I've found out there is a
separate project automake (I mistakenly thought this was part of the
autoconf project). It also explains why I was having difficulty
locating the Makefile.am transformation macros :-)

regards,
Gaius