there are
not as I'm not expert enough to know one way or another.
Patrick
--
View this message in context:
http://gnu-make.2324884.n4.nabble.com/file-function-bug-or-not-tp15161p15213.html
Sent from the Gnu - Make - Bugs mailing list archive at Nabble.com
:
http://gnu-make.2324884.n4.nabble.com/file-function-bug-or-not-tp15161p15213.html
Sent from the Gnu - Make - Bugs mailing list archive at Nabble.com.
___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
this message in context:
http://gnu-make.2324884.n4.nabble.com/file-function-bug-or-not-tp15161p15213.html
Sent from the Gnu - Make - Bugs mailing list archive at Nabble.com.
___
Bug-make mailing list
Bug-make@
https://lists.gnu.org/mailman
I'm trying to understand if my use of the $(file..) function is correct or
not. Based on tests/scripts/function/file, I cooked up this little file.mak:
all: file_test
cat file.out
.PHONY: file_test
file_test:
rm file.out
$(file file.out, Hello)
$(file file.out, world)
@echo 'abspath
Paul Smith psm...@gnu.org wrote:
Then make invokes the shell with the results of the expansion, which are
the rm and echo commands (and some empty strings which are ignored).
So, the rm is running AFTER the file is created, and deleting it.
Thanks. That makes sense when I think about it.
On Tue, Jan 28, 2014 at 7:31 AM, Gisle Vanem gva...@yahoo.no wrote:
Paul Smith psm...@gnu.org wrote:
Then make invokes the shell with the results of the expansion, which are
the rm and echo commands (and some empty strings which are ignored).
So, the rm is running AFTER the file is created,
On Tue, 2014-01-28 at 09:52 -0800, David Boyce wrote:
I think the headline here is that $(file) is analogous to $(shell) in
that it's intended specifically for use _outside_ of recipes. If you
find yourself using either one in a recipe it's probably a sign you're
on the wrong track.
I'm not
On Tue, Jan 28, 2014 at 1:20 PM, Paul Smith psm...@gnu.org wrote:
I'm not sure I'd go that far. $(shell ...) really _is_ useless in a
recipe because make will invoke a shell to run the recipe anyway, so why
have it invoke two shells? It's just redundant.
However, $(file ...) can be useful
