Makefile best practices for embedded development

[Dan Kegel]

Doug Evans wrote:
> Newer gcc's have much better (IMO, YMMV) support for generating dependency
> information.  Typical use is to generate dependencies at build time and put
> them into separate files that are included by the Makefile.
> It's a chicken-and-egg situation that is resolved by the fact that
> one begins with a clean directory (so everything needs to be built from
> scratch anyway) and "-include" is used to include the dependency files
> (so make doesn't complain if they don't exist).
> I've seen it work extremely well in practice with two caveats:
> dependencies on machine-generated files still need to be explicitly stated,

The machine-generated file problem applies to .h files that are installed,
I've found.  If you want good dependencies, you probably want to
include your .h files from where they live in the source tree rather
than including their installed versions.
Just a note of caution...
I posted a test case for this problem at http://mail.gnu.org/archive/html/help-make/2003-09/msg00037.html
- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com