🚀 go-pugleaf

In article <21cukd$lbq@truffula.fp.trw.com> awick@truffula.fp.trw.com (Andy Wick) writes:
>
>What are the pros and cons of -I's vs relative includes?
>
>[lots of include files spread over many directories]
>
>[What's better:]
>    [(a) have #include statements contain relative paths to each file]
>    [(b) use -I option to specify each directory include files may appear]

I just started using another option; creating a separate project/include
directory and putting a mechanism in each source directory's makefile to 
"install" the include files there; and can then access all of them
with a single -I option.  The advantage is that if I am developing a
newer version of the software which needs changes to the include files
I can simply put them somewhere like myhomedirectory/include, and
access them with a single additional -I option.  The disadvantage is
that you need to do a "make install_includes" in each directory before
compilation will work on a new source tree.

    Ron Mayer
    mayer@acuson.com