+2001-07-16 Tom Tromey <tromey@redhat.com>
+
+ * automake.texi (Program and Library Variables): Document _LINK.
+
2001-07-16 Alexandre Duret-Lutz <duret_g@epita.fr>
* automake.in (handle_libraries): Allow libraries to lie in
This variable is used to pass extra flags to the link step of a program
or a shared library.
+@item maude_LINK
+You can override the linker on a per-program basis. By default the
+linker is chosen according to the languages used by the program. For
+instance, a program that includes C++ source code would use the C++
+compiler to link. The @samp{_LINK} variable must hold the name of a
+command which can be passed all the @file{.o} file names as arguments.
+Note that the name of the underlying program is @emph{not} passed to
+@samp{_LINK}; typically one uses @samp{$@@}:
+
+@example
+maude_LINK = $(CCLD) -magic -o $@
+@end example
+
@item maude_CFLAGS
Automake allows you to set compilation flags on a per-program (or
per-library) basis. A single source file can be included in several
In compilations with per-program flags, the ordinary @samp{AM_} form of
the flags variable is @emph{not} automatically included in the
-compilation (however, the user form of the variable @emph{is}
-included). So for instance, if you want the hypothetical @file{maude}
-compilation to also use the value of @samp{AM_CFLAGS}, you would need to
-write:
+compilation (however, the user form of the variable @emph{is} included).
+So for instance, if you want the hypothetical @file{maude} compilations
+to also use the value of @samp{AM_CFLAGS}, you would need to write:
@example
maude_CFLAGS = ... your flags ... $(AM_CFLAGS)