Hi,
this seems to be by design, to overcome the fact that
OBJECTS = *.o
doesn't expand the list, whereas
OBJECTS = $(wildcard *.o)
does. $(wildcard is expanded upon the first pass over the makefile, ie. when
no rules have been executed yet; so your 'testfile' doesn't yet exist, and
Hi Johan :)
I'm writing to the bug mailinglist so anybody can read the
message, ok?, but really is for you ;)
this seems to be by design, to overcome the fact that
OBJECTS = *.o
doesn't expand the list, whereas
OBJECTS = $(wildcard *.o)
does.
Yes, I know, it is very
%% Johan Bezem [EMAIL PROTECTED] writes:
jb this seems to be by design, to overcome the fact that
jb OBJECTS = *.o
jb doesn't expand the list, whereas
jb OBJECTS = $(wildcard *.o)
jb does. $(wildcard is expanded upon the first pass over the
jb makefile, ie. when no rules have
Hi Paul :)
Why doesn't it
work? It doesn't work because GNU make actually caches the contents of
directories as it reads them, for performance reasons.
I supposed that some caching was the cause, but for me was
reasonable that $wildcard will not expand if the new file wasn't
cached.
Johan Bezem [EMAIL PROTECTED] wrote:
DervishD wrote:
Will this undesired
behaviour (undesired by me, at least) be solved if I replace
$(wildcard pattern) with $(shell echo pattern)?
No, you'd probably need 'ls', 'echo' just echoes the given characters, and
uses no wildcard expansion AFAIK,
Paul D. Smith wrote:
%% Johan Bezem [EMAIL PROTECTED] writes:
jb this seems to be by design, to overcome the fact that
jb OBJECTS = *.o
jb doesn't expand the list, whereas
jb OBJECTS = $(wildcard *.o)
jb does. $(wildcard is expanded upon the first pass over the