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

[Neulinger, Nathan]

I kindof figured we'd want to install the afsconfig.h file in a way similar
to param.h, since that is what is being used now.

Now, if the makefiles can be modified to search for it in dest/include
instead of dest/include/afs, then I see nothing wrong with it being in the
top level.

Also, I don't have any objection to modifying the makefiles as those
directories are converted to use the afsconfig.h file. That might be the
easiest approach, although setting an include once at the top level sure
would be nice.

-- 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
>