Attachment #47353 for issue #66448

View | Details | Raw Unified | Return to issue 66448
Collapse All | Expand All




	    }
	 }
	 else {
	    /* The inference mechanism for %-targets limits the number of
	     * (non-indirect) prerequisite to one, but an unlimited number
	     * of indirect prerequisites is possible. */
	     * if multiple prerequisites are provided. */
	    if ( nprq && nprq->ce_link && !(op & R_OP_OR))
	       Warning("More than one prerequisite\n"
	       "for %%-target. Use :| ruleop or indirect prerequisites.");
	       "Check your makefiles!.\n");

	    _build_graph(op,tg1,nprq);
	 }







Dmake Version 4.11-cvs            2007-08-06                                 1







Dmake Version 4.11-cvs            2007-08-06                                 2







Dmake Version 4.11-cvs            2007-08-06                                 3







Dmake Version 4.11-cvs            2007-08-06                                 4







Dmake Version 4.11-cvs            2007-08-06                                 5







Dmake Version 4.11-cvs            2007-08-06                                 6







Dmake Version 4.11-cvs            2007-08-06                                 7







Dmake Version 4.11-cvs            2007-08-06                                 8







Dmake Version 4.11-cvs            2007-08-06                                 9







Dmake Version 4.11-cvs            2007-08-06                                10







Dmake Version 4.11-cvs            2007-08-06                                11







Dmake Version 4.11-cvs            2007-08-06                                12







Dmake Version 4.11-cvs            2007-08-06                                13







Dmake Version 4.11-cvs            2007-08-06                                14







Dmake Version 4.11-cvs            2007-08-06                                15







Dmake Version 4.11-cvs            2007-08-06                                16







Dmake Version 4.11-cvs            2007-08-06                                17







Dmake Version 4.11-cvs            2007-08-06                                18







Dmake Version 4.11-cvs            2007-08-06                                19







Dmake Version 4.11-cvs            2007-08-06                                20







Dmake Version 4.11-cvs            2007-08-06                                21







Dmake Version 4.11-cvs            2007-08-06                                22







Dmake Version 4.11-cvs            2007-08-06                                23







Dmake Version 4.11-cvs            2007-08-06                                24







Dmake Version 4.11-cvs            2007-08-06                                25







Dmake Version 4.11-cvs            2007-08-06                                26







Dmake Version 4.11-cvs            2007-08-06                                27







Dmake Version 4.11-cvs            2007-08-06                                28







Dmake Version 4.11-cvs            2007-08-06                                29







Dmake Version 4.11-cvs            2007-08-06                                30







Dmake Version 4.11-cvs            2007-08-06                                31







Dmake Version 4.11-cvs            2007-08-06                                32







Dmake Version 4.11-cvs            2007-08-06                                33







Dmake Version 4.11-cvs            2007-08-06                                34







Dmake Version 4.11-cvs            2007-08-06                                35







Dmake Version 4.11-cvs            2007-08-06                                36







Dmake Version 4.11-cvs            2007-08-06                                37







Dmake Version 4.11-cvs            2007-08-06                                38







Dmake Version 4.11-cvs            2007-08-06                                39




       the %-meta rule when the rule is selected during  inference  and  dmake
       constructs the new dependency.

       Please  note,  that  only  the first, non-indirect, prerequisite of the
       list is used for the inference mechanism. If more than one non-indirect
       prerequisite  is  given  a warning is issued and all but the first non-
       indirect prerequisites are ignored. See  below  for  a  description  of
       indirect prerequisites.

       As an example the following %-meta rules describe the following:


       describes how to make a file whose suffix is .a without  inferring  any
       prerequisites.

              %.c : %.y 'yaccsrc/%.y' ; recipe...

       matches  the  corresponding  .y  file  as prerequisite and additionally
       another .y file in the yaccsrc subdirectory as  indirect  prerequisite.
       Another interesting example is:

              % : RCS/%,v ; co $<

       dmake  supports  dynamic  prerequisite  generation for prerequisites of
       %-meta rules.  This is best illustrated by an example.   The  RCS  rule
       shown  above can infer how to check out a file from a corresponding RCS
       file only if the target  is  a  simple  file  name  with  no  directory
       mation.   That  is,  the  above rule can infer how to find RCS/fred.c,v
       from   the   target   fred.c,   but   cannot   infer   how   to    find



Dmake Version 4.11-cvs            2007-08-06                                40




DMAKE(1)                                                              DMAKE(1)


       information.    That   is,  the  above  rule  can  infer  how  to  find
       RCS/fred.c,v from the target fred.c,  but  cannot  infer  how  to  find
       srcdir/RCS/fred.c,v  from  srcdir/fred.c  because  the  above rule will
       cause dmake to look  for  RCS/srcdir/fred.c,v;  which  does  not  exist
       (assume that srcdir has its own RCS directory as is the common case).

       get.  They do not play an active role in driving  the  inference  algo-
       rithm.  The construct:

              %.o : %.c %.f 'local.h'; recipe

       is (currently) equivalent to:

              %.o : %.c 'local.h' ; recipe

       because the second prerequisite is ignored, while:

              %.o :| %.c %.f 'local.h'; recipe

       is equivalent to:

       then when that rule is bound to a target as the result of an inference,
       the target's set of attributes is augmented by the attributes from  the
       above  set  that  are  specified in the bound %-rule.  Other attributes
       specified for %-meta rules are not inherited by the target.  The  .SET-
       DIR attribute is treated in a special way.  If the target already had a
       .SETDIR attribute set then dmake changes to  that  directory  prior  to
       performing  the inference.  During inference any .SETDIR attributes for
       the inferred prerequisite are honored.  The directories must exist  for
       a  %-meta  rule  to  be  selected as a possible inference path.  If the
       directories do not exist  no  error  message  is  issued,  instead  the



Dmake Version 4.11-cvs            2007-08-06                                41




DMAKE(1)                                                              DMAKE(1)


       corresponding path in the inference graph is rejected.
       had a .SETDIR attribute set then dmake changes to that directory  prior
       to  performing  the inference.  During inference any .SETDIR attributes
       for the inferred prerequisite are honored.  The directories must  exist
       for  a %-meta rule to be selected as a possible inference path.  If the
       directories do not exist no error message is issued, instead the corre-
       sponding path in the inference graph is rejected.

       dmake  bases  all  of its inferences on the inference graph constructed
       from the %-rules defined in the makefile.  It knows exactly which  tar-

       not given on the command line, and if the inferred intermediate did not
       previously  exist.   Intermediate  targets  that existed prior to being
       made are never removed.  This is in keeping with  the  philosophy  that
       dmake  should  never remove things from the file system that it did not
       add.  If the special target .REMOVE is defined and has  a  recipe  then
       dmake  constructs  a  list  of the intermediate files to be removed and
       makes them prerequisites of .REMOVE.  It  then  makes  .REMOVE  thereby
       removing the prerequisites if the recipe of .REMOVE says to.  Typically
       .REMOVE is defined in the startup file as:



Dmake Version 4.11-cvs            2007-08-06                                42




DMAKE(1)                                                              DMAKE(1)


       dmake  should  never remove things from the file system that it did not
       add.  If the special target .REMOVE is defined and has  a  recipe  then
       dmake  constructs  a  list  of the intermediate files to be removed and
       makes them prerequisites of .REMOVE.  It  then  makes  .REMOVE  thereby
       removing the prerequisites if the recipe of .REMOVE says to.  Typically
       .REMOVE is defined in the startup file as:

              .REMOVE :; $(RM) $<

AUGMAKE META RULES

       was in before the command was executed.

       The  decision  on  whether  a shell is required to execute a command is
       based on the value of the macro SHELLMETAS or on the  specification  of
       '+' or .USESHELL for the current recipe or target respectively.  If any
       character in the value of SHELLMETAS is found in  the  expanded  recipe
       text-line  or  the  use  of  a shell is requested explicitly via '+' or
       .USESHELL then the command is executed using  a  shell,  otherwise  the
       command  is executed directly.  The shell that is used for execution is
       given by the value of the macro SHELL.  The flags that  are  passed  to



Dmake Version 4.11-cvs            2007-08-06                                43




DMAKE(1)                                                              DMAKE(1)


       based on the value of the macro SHELLMETAS or on the  specification  of
       '+' or .USESHELL for the current recipe or target respectively.  If any
       character in the value of SHELLMETAS is found in  the  expanded  recipe
       text-line  or  the  use  of  a shell is requested explicitly via '+' or
       .USESHELL then the command is executed using  a  shell,  otherwise  the
       command  is executed directly.  The shell that is used for execution is
       given by the value of the macro SHELL.  The flags that  are  passed  to
       the  shell are given by the value of SHELLFLAGS.  Thus dmake constructs
       the command line:


       which has a much shorter argument list.  It is now up to the command to
       use the supplied argument as the source for all other arguments.  As an
       optimization, if COMMAND is not defined  dmake  does  not  perform  the
       above  expansion.   On  systems, such as UNIX, that handle long command
       lines this provides a slight saving in processing the makefiles.

MAKING LIBRARIES
       Libraries are easy to maintain using dmake.  A library is a  file  con-
       taining  a collection of object files.  Thus to make a library you sim-
       ply specify it as a target with the .LIBRARY attribute set and  specify



Dmake Version 4.11-cvs            2007-08-06                                44




DMAKE(1)                                                              DMAKE(1)


       above  expansion.   On  systems, such as UNIX, that handle long command
       lines this provides a slight saving in processing the makefiles.

MAKING LIBRARIES
       Libraries are easy to maintain using dmake.  A library is a  file  con-
       taining  a collection of object files.  Thus to make a library you sim-
       ply specify it as a target with the .LIBRARY attribute set and  specify
       its list of prerequisites.  The prerequisites should be the object mem-
       bers that are to go into the library.  When  dmake  makes  the  library
       target  it uses the .LIBRARY attribute to pass to the prerequisites the


       NOTE:  If the notion of entry points is supported by the archive and by
       dmake  (currently  not the case) then dmake will search the archive for
       the entry point and return not only the modification time of the member
       which  defines  the  entry  but also the name of the member file.  This
       name will then replace entry and will be used  for  making  the  member
       file.  Once bound to an archive member the .SYMBOL attribute is removed
       from the target.  This feature is presently disabled as there is little
       standardization  among archive formats, and we have yet to find a make-
       file utilizing this feature (possibly  due  to  the  fact  that  it  is



Dmake Version 4.11-cvs            2007-08-06                                45




DMAKE(1)                                                              DMAKE(1)


       unimplemented in most versions of UNIX Make).
       which  defines  the  entry  but also the name of the member file.  This
       name will then replace entry and will be used  for  making  the  member
       file.  Once bound to an archive member the .SYMBOL attribute is removed
       from the target.  This feature is presently disabled as there is little
       standardization  among archive formats, and we have yet to find a make-
       file utilizing this feature (possibly due to the fact that it is  unim-
       plemented in most versions of UNIX Make).

       Finally, when dmake looks for a library member it must first locate the
       library file.  It does so by first looking for the library relative  to

       be removed.  If a parallel make is being performed then  the  following
       restrictions on parallelism are enforced.

              1.     Individual  recipe  lines  in a non-group recipe are per-
                     formed sequentially in the order in which they are speci-
                     fied within the makefile and in parallel with the recipes
                     of other targets.

              2.     If a target contains multiple recipe definitions (cf.  ::
                     rules) then these are performed sequentially in the order

Dmake Version 4.11-cvs            2007-07-05                                46


Dmake Version 4.11-cvs            2007-08-06                                46



DMAKE(1)                                                              DMAKE(1)


DMAKE(1)                                                              DMAKE(1)

                     fied within the makefile and in parallel with the recipes
                     of other targets.

              2.     If a target contains multiple recipe definitions (cf.  ::
                     rules) then these are performed sequentially in the order
                     in which the :: rules are specified within  the  makefile
                     and in parallel with the recipes of other targets.


       numerical part is found this results to 0 (zero). The string "12ab" for
       example  evaluates to the number 12.  Expressions can be nested with ()
       and the use of || or &&.  White space at the start and end of the  text
       portion  is  discarded  before the comparison.  This means that a macro
       that evaluates to nothing but white space is considered  a  NULL  value
       for  the  purpose  of the comparison.  In the first case the expression
       evaluates TRUE if the text is not NULL otherwise  it  evaluates  FALSE.
       The  remaining two cases both evaluate the expression on the basis of a
       string comparison.  If a macro expression needs to be equated to a NULL
       string  then compare it to the value of the macro $(NULL).  You can use
       the $(shell ...) macro to construct more complex test expressions.



Dmake Version 4.11-cvs            2007-08-06                                47




DMAKE(1)                                                              DMAKE(1)


       portion  is  discarded  before the comparison.  This means that a macro
       that evaluates to nothing but white space is considered  a  NULL  value
       for  the  purpose  of the comparison.  In the first case the expression
       evaluates TRUE if the text is not NULL otherwise  it  evaluates  FALSE.
       The  remaining two cases both evaluate the expression on the basis of a
       string comparison.  If a macro expression needs to be equated to a NULL
       string  then compare it to the value of the macro $(NULL).  You can use
       the $(shell ...) macro to construct more complex test expressions.

EXAMPLES
              # A simple example showing how to use make
              #

       An example of building library members would go  something  like  this:
       (NOTE:  The same rules as above will be used to produce .o's from .c's)

              SRC= a b
              LIB= lib
              LIBm= { $(SRC) }.o

              prgm: $(LIB)
                   cc -o $@ $(LIB)

              $(LIB) .LIBRARY : $(LIBm)
                   ar rv $@ $<

Dmake Version 4.11-cvs            2007-07-05                                48


Dmake Version 4.11-cvs            2007-08-06                                48



DMAKE(1)                                                              DMAKE(1)


DMAKE(1)                                                              DMAKE(1)
              LIB= lib
              LIBm= { $(SRC) }.o

              prgm: $(LIB)
                   cc -o $@ $(LIB)

              $(LIB) .LIBRARY : $(LIBm)
                   ar rv $@ $<
                   rm $<

       Finally, suppose that each of the source files in the previous  example

                 the restriction that str must  match  the  following  regular
                 expression:

                 str[ |\t][ |\t]*

                 (ie.  str  only  matches at the end of a token where str is a
                 suffix and is terminated by a space, a tab, or end  of  line)
                 Normally  sub is expanded before the substitution is made, if
                 you specify -A on the command line then sub is not  expanded.

              3. The  macro  % is defined to be $@ (ie. $% expands to the same
                 value as $@).

Dmake Version 4.11-cvs            2007-07-05                                49



Dmake Version 4.11-cvs            2007-08-06                                49


DMAKE(1)                                                              DMAKE(1)


                 str[ |\t][ |\t]*

DMAKE(1)                                                              DMAKE(1)
                 suffix and is terminated by a space, a tab, or end  of  line)
                 Normally  sub is expanded before the substitution is made, if
                 you specify -A on the command line then sub is not  expanded.

              3. The  macro  % is defined to be $@ (ie. $% expands to the same
                 value as $@).

              4. The AUGMAKE notion of libraries is handled correctly.


AUTHOR
       Dennis Vadura, dvadura@wticorp.com
       Many thanks to Carl Seger for his helpful suggestions,  and  to  Trevor
       John Thompson for his many excellent ideas and informative bug reports.
       Many thanks also go to those on the NET  that  have  helped  in  making
       dmake one of the best Make tools available.

BUGS
       Some  system  commands  return non-zero status inappropriately.  Use -i
       (`-' within the makefile) to overcome the difficulty.

       Some systems do not have easily accessible time stamps for library mem-
       bers  (MSDOS,  AMIGA,  etc)  for these dmake uses the time stamp of the

Dmake Version 4.11-cvs            2007-07-05                                50


Dmake Version 4.11-cvs            2007-08-06                                50



DMAKE(1)                                                              DMAKE(1)


DMAKE(1)                                                              DMAKE(1)
       Many thanks also go to those on the NET  that  have  helped  in  making
       dmake one of the best Make tools available.

BUGS
       Some  system  commands  return non-zero status inappropriately.  Use -i
       (`-' within the makefile) to overcome the difficulty.

       Some systems do not have easily accessible time stamps for library mem-
       bers  (MSDOS,  AMIGA,  etc)  for these dmake uses the time stamp of the
       library instead and prints a warning the first time it does  so.   This
       is  almost  always  ok,  except when multiple makefiles update a single
       library file.  In these instances it is possible to miss an  update  if














Dmake Version 4.11-cvs            2007-08-06                                51



Lines 19-25 Link Here

(-)dmake/man/dmake.tf (-20 / +8 lines)
19	.IP "\\$1" \\n[dmake-indent]u	19	.IP "\\$1" \\n[dmake-indent]u
20	.it 1 PD	20	.it 1 PD
21	..	21	..
22	.TH DMAKE 1 "2007-07-05" "Dmake Version 4.11-cvs"	22	.TH DMAKE 1 "2007-08-06" "Dmake Version 4.11-cvs"
23	.SH NAME	23	.SH NAME
24	\fBdmake\fR \- maintain program groups, or interdependent files	24	\fBdmake\fR \- maintain program groups, or interdependent files
25	.SH SYNOPSIS	25	.SH SYNOPSIS
Lines 2551-2558 Link Here
2551	constructs the new dependency.	2551	constructs the new dependency.
2552	.PP	2552	.PP
2553	.B Please note,	2553	.B Please note,
2554	that currently only the first, non-indirect, prerequisite of the	2554	that only the first, non-indirect, prerequisite of the list is used for the
2555	list is used and all other non-indirect prerequisites are ignored.	2555	inference mechanism. If more than one non-indirect prerequisite is given
		2556	a warning is issued and all but the first non-indirect prerequisites are
		2557	ignored. See below for a description of indirect prerequisites.
2556	.PP	2558	.PP
2557	As an example the following %-meta rules describe the following:	2559	As an example the following %-meta rules describe the following:
2558	.RS	2560	.RS
Lines 2577-2587 Link Here
2577	prerequisites.	2579	prerequisites.
2578	.RS	2580	.RS
2579	.sp	2581	.sp
2580	%.c : %.y yaccsrc/%.y ; recipe...	2582	%.c : %.y 'yaccsrc/%.y' ; recipe...
2581	.sp	2583	.sp
2582	.RE	2584	.RE
2583	should match the corresponding .y file and another .y file in the yaccsrc	2585	matches the corresponding .y file as prerequisite and additionally another .y
2584	subdirectory. (Currently only the first prerequisite is used.)	2586	file in the yaccsrc subdirectory as indirect prerequisite.
2585	Another interesting example is:	2587	Another interesting example is:
2586	.RS	2588	.RS
2587	.sp	2589	.sp
Lines 2684-2703 Link Here
2684	The construct:	2686	The construct:
2685	.RS	2687	.RS
2686	.sp	2688	.sp
2687	%.o : %.c %.f 'local.h'; recipe
2688	.sp
2689	.RE
2690	is (currently) equivalent to:
2691	.RS
2692	.sp
2693	.nf
2694	%.o : %.c 'local.h' ; recipe
2695	.fi
2696	.sp
2697	.RE
2698	because the second prerequisite is ignored, while:
2699	.RS
2700	.sp
2701	%.o :\| %.c %.f 'local.h'; recipe	2689	%.o :\| %.c %.f 'local.h'; recipe
2702	.sp	2690	.sp
2703	.RE	2691	.RE

Return to issue 66448

Lines 943-956 Link Here

(-)dmake/rulparse.c (-6 / +4 lines)
943	}	943	}
944	}	944	}
945	else {	945	else {
946	/* Multiple prerequisits require all of them match for this	946	/* The inference mechanism for %-targets limits the number of
947	* %-target to be chosen. */	947	* (non-indirect) prerequisite to one, but an unlimited number
948	/* FIXME: There seem to be problems in the target inference	948	* of indirect prerequisites is possible. */
949	* if multiple prerequisites are provided. */
950	if ( nprq && nprq->ce_link && !(op & R_OP_OR))	949	if ( nprq && nprq->ce_link && !(op & R_OP_OR))
951	Warning("More than one prerequisite\n"	950	Warning("More than one prerequisite\n"
952	"for %%-target without :\| as ruleop. Only the first is currently used.\n"	951	"for %%-target. Use :\| ruleop or indirect prerequisites.");
953	"Check your makefiles!.\n");
954		952
955	_build_graph(op,tg1,nprq);	953	_build_graph(op,tg1,nprq);
956	}	954	}