l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Mar 31 15:15

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

I would expect that a choice to do such a thing in a makefile makes little
sense to most users who would use it. Few people would ever modify the
header files at all. Testing of the header files would likely be done by
the developers.

Making a makefile option for "debug:" which includes deps for the heads
you are actually altering as well as -ggdb (etc) for debugging for

I generally have separate projects which test my own custom header files
separate from the project which is using them. Then, there is no need to
check the headers files for modification since they should not be modified
if they were properly tested. (Test the custom classes/headers extensively
so that projects relying upon them don't have weird surprises... the idea
of ensuring your foundations are solid before trying to build upon them.)

I'd like to see what others say about this though.


Bill Kendrick said:
> 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?
> 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...?
> I just want to make sure that in case I touch something somewhere, that
> everybody who needs to get update GETS updated.
> Thx!
> -bill!
> bill@newbreedsoftware.com              Have you visited the Linux Users'
> Group
> http://newbreedsoftware.com/bill/        of Davis yet!?
> http://www.lugod.org/
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
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.