mirror of
https://git.savannah.gnu.org/git/make.git
synced 2024-12-25 05:29:46 +00:00
* doc/make.text (Wildcards): Document that glob results are sorted.
This commit is contained in:
parent
1d20aa7247
commit
55b993ae09
1 changed files with 12 additions and 0 deletions
|
@ -2142,6 +2142,13 @@ The wildcard characters in @code{make} are @samp{*}, @samp{?} and
|
|||
specifies a list of all the files (in the working directory) whose names
|
||||
end in @samp{.c}.@refill
|
||||
|
||||
If an expression matches multiple files than the results will be
|
||||
sorted.@footnote{Some older versions of GNU @code{make} did not sort the
|
||||
results of wildcard expansion.} However multiple expressions will not be
|
||||
globally sorted. For example, @file{*.c *.h} will list all the files whose
|
||||
names end in @samp{.c}, sorted, followed by all the files whose names end in
|
||||
@samp{.h}, sorted.
|
||||
|
||||
@cindex @code{~} (tilde)
|
||||
@cindex tilde (@code{~})
|
||||
@cindex home directory
|
||||
|
@ -2309,6 +2316,11 @@ function. Note that this is different from how unmatched wildcards
|
|||
behave in rules, where they are used verbatim rather than ignored
|
||||
(@pxref{Wildcard Pitfall}).
|
||||
|
||||
As with wildcard expansion in rules, the results of the @code{wildcard}
|
||||
function are sorted. But again, each individual expression is sorted
|
||||
separately, so @samp{$(wildcard *.c *.h)} will expand to all files matching
|
||||
@samp{.c}, sorted, followed by all files matching @samp{.h}, sorted.
|
||||
|
||||
One use of the @code{wildcard} function is to get a list of all the C source
|
||||
files in a directory, like this:
|
||||
|
||||
|
|
Loading…
Reference in a new issue