Lines Matching refs:programs

34 describes conventions for writing the Makefiles for GNU programs.
62 Different @code{make} programs have incompatible suffix lists and
77 you need to run programs that are a part of your package during the
163 Stick to the generally supported options for these programs.  For
171 and related programs, but should do so via @code{make} variables so that the
172 user can substitute alternatives.  Here are some of the programs we
180 Use the following @code{make} variables to run those programs:
213 In particular, you should run most utility programs via variables.
220 don't need to replace them with other programs.
333 Executable programs are installed in one of the following directories.
338 The directory for installing executable programs that users can run.
345 The directory for installing executable programs that can be run from
354 The directory for installing executable programs to be run by other
355 programs rather than by users.  This directory should normally be
365 Some files are normally modified by programs; others are never normally
403 files that are modified in the normal course of their use (programs
409 the programs modify while they run.  This should normally be
414 The directory for installing data files which the programs modify while
453 programs with the C @samp{#include} preprocessor directive.  This
562 All GNU programs should have the following targets in their Makefiles:
572 that executable programs have debugging symbols.  Users who don't mind
796 The following targets are suggested as conventional names, for programs
868 Most programs don't need any pre-installation commands, but we have the
915 programs except for these: