[OpenAFS-devel] initial afsconfig.h.in patch

[Neulinger, Nathan]

Did you come up with any ideas on this?

Another option if you prefer... I could adjust the patch to have the top
level makefile pass an additional variable along to all the submakes
"top_srcdir", which is what autoconf/automake uses. (It also uses srcdir,
but that tracks with the subdirectory you are in. This would enable easily
adding a:

-I$(top_srcdir)/config

to any CCOPTS in submakes as needed, which would work identically in all
dirs.

-- Nathan

> -----Original Message-----
> From: Derrick J Brashear [mailto:shadow@dementia.org]
> Sent: Monday, April 30, 2001 2:08 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] initial afsconfig.h.in patch
> 
> 
> On 30 Apr 2001, Russ Allbery wrote:
> 
> > Nathan Neulinger <nneul@umr.edu> writes:
> > 
> > > I started modifying afsd.c to make use of the afs/afsconfig.h
> > > include. For now, it's being included as #include 
> <afs/afsconfig.h>, but
> > > when the autoconf stuff is developed, I think that the 
> Makefile should
> > > be doing -I$(srcdir) etc. and just use #include "afsconfig.h".
> > 
> > For what it's worth, autoconf recommends against ever using 
> "" for include
> > files since it interferes with srcdir != builddir builds.  
> Not sure how
> > much we care.
> 
> As long as the config file isn't named config.h using <> 
> shouldn't be a
> problem; But use of afs/afsconfig.h is suboptimal. 
> 
> -D
> 
> 
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel
>