l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
November 4: Social gathering
Next Installfest:
TBD
Latest News:
Oct. 10: LUGOD Installfests coming again soon
Page last updated:
2004 Mar 31 15:48

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Make question: headers depending on other headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Make question: headers depending on other headers



On Wed, 31 Mar 2004, Bill Kendrick wrote:

> 
> I have some source files that depend on some other sources' headers.
> 
> In turn, some of THOSE headers depend on other headers (e.g., a header
> defining a structure might depend on another header that defines some other
> structures).
> 
> Is it useful to list these 'dependencies' within the Makefile?

That is what a makefile is all about.

> For example, consider foo.c:
> 
>   /* foo.c
>      I do foo things */
> 
>   #include "foo.h"  /* My header */
>   #include "bar.h"  /* bar.c's header, so I can get to its function(s) and/or
>                        typedefs... */
> 
>   ...
> 
> 
> In Makefile, I'd do:
> 
>   foo.o:  foo.c foo.h bar.h
>           ...compile foo.c into foo.o...
> 
> 
> However, say in "bar.h", I have:
> 
> 
>   /* bar.h
>      I do things with alcohol (get it? "bar?" hahaha...) */
> 
>   #include "bar.h"  /* My header */
>   #include "zzz.h"  /* Contains some #define's for compile-time options */
> 
>   ...
> 
> 
> Should I make "bar.h" depend on "zzz.h"?  Or "foo.o" depend on it?  Or...?

You have bar.h including bar.h... not a good idea.  I am not really sure
where your question was leading... assuming we omit the recursion...

* the foo.c dependency should include foo.h, bar.h, and zzz.h

* any bar.c dependency should include bar.h and zzz.h

> I just want to make sure that in case I touch something somewhere, that
> everybody who needs to get update GETS updated.

In general, for a given .c.o dependency, you need to include all of the
quoted includes that it depends on... directly OR indirectly. This is
generally not done for <> includes (library headers).

---------------------------------------------------------------------------
Jeff Newmiller                        The     .....       .....  Go Live...
DCN:<jdnewmil@dcn.davis.ca.us>        Basics: ##.#.       ##.#.  Live Go...
                                      Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/Batteries            O.O#.       #.O#.  with
/Software/Embedded Controllers)               .OO#.       .OO#.  rocks...2k
---------------------------------------------------------------------------


_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.