It's not dry when the command in question is a recursive call to make either.
That's because, in both cases, it's more useful to more people to behave this
way by default. If you want a different behavior, you can have your including
makefile decide not to include if the included file doesn't exist and
MAKECMDFLAGS contains n. I agree that that is sometimes useful.
----- Original Message -----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: bug-make@gnu.org <bug-make@gnu.org>
Sent: Mon Sep 01 05:34:47 2008
Subject: dry-run (-n) has no effect with include file generation
Hi,
I noticed that 'make -n' (dry run) is not always like dry, like
mentioned in the help:
-n, --just-print, --dry-run, --recon
Don't actually run any commands; just print them.
In my case I have an include statement, which include files which
aren't available at make-start-time, but make knows how to generate
them.
Thus the bug is: If I run 'make -n' then the commands to generate the included
files are actually run.
I am using make 3.81.
Best regards
Georg Sauthoff
--
Fortune : 'Real programmers don't comment their code.
It was hard to write, it should be hard to understand.' ;)
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
