> > OK, I badly answered the above question! > HEADERS = a.h b.h c.h > just creates an environment variable with a list of text > (file names in this case). > HEADERS: a.h b.h c.h > would create a list of dependencies for HEADERS, so that HEADERS > would be rebuilt if any of those files listed showed a newer > revision > date than HEADERS. >
Thanks for clarifying. My original question was poorly put as well. What I was trying ask is not so much what that specific syntax does, but why the Makefile has a hard-coded list, instead of automatically gathering all of the .h files. Similarly, there's a SUBDIRS variable that manually specifies all of the locations to search for SubMakefiles. Is this because there are some subdirectories we'd like to ignore? If not, it seems like this variable could be automatically generated as well. The reason I ask is that I'd be willing to take a look at making these variables automatically if it's something that simply hasn't been done yet. HEADERS := <something> is not a syntax I can locate in any docs > for make. Does it do something different? > > I am just barely able to create simple Makefiles. The ":=" syntax seems to be explained here: http://www.gnu.org/software/make/manual/make.html#Reading-Makefiles Apparently it controls whether an expression is immediately expanded or deferred until the variable is actually needed. -Rob ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
