1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: What I learned today... |
From: | Benjamin Franksen <[email protected]> |
To: | <[email protected]> |
Date: | Fri, 1 Mar 2013 12:55:55 +0100 |
On Thursday, February 28, 2013 10:51:51 Michael Davidsaver wrote: > On 02/28/2013 09:57 AM, Benjamin Franksen wrote: > > On Thursday, February 28, 2013 09:41:14 Michael Davidsaver wrote: > >> Makefiles are so much fun... > >> > >> If you don't like creating marker files (which must be cleaned) you can > >> > >> also do: > >>> one two three: create_some_files.pl > >>> > >>> ./create_some_files.pl > >>> > >>> three: two > >>> two: one > >> > >> This creates a dependency chain forcing sequential execution. > > > > Yes, but... > > > (1) The script can be called more often than necessary: > I don't think this is the case as long as the command > './create_some_files.pl' creates all three files (which I assume it what > you intended). I attached a simple test example that exhibits the above behaviour. Cheers -- Ben Franksen () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
all: one two three one two three: create_some_files.sh ./create_some_files.sh three: two two: one clean: rm -f one two three files_created
Attachment:
create_some_files.sh
Description: application/shellscript
Attachment:
signature.asc
Description: This is a digitally signed message part.