[OpenAFS-devel] Re: [OpenAFS] jafs et al

[Derrick J Brashear]

On Wed, 14 Mar 2007, Marcus Watts wrote:

> A lot of these *-config things were probably generated by some gnu tool
> (libtool?), but AFS will probably need its own unique thing.  I envision
> something that might work like this:

I keep considering this. The only problem is how to encode the path for 
destdir builds. I suppose we could provide a one time script which you run 
with the full path of the script, it confirms the install is really there, 
edits the config script and then nukes itself.


> 	% openafs-config --libs pt ka
> 	-L/usr/afs/lib -lprot -lkauth -lubik -lrxkad -lrx -ldes -lcom_err -lafsutil
> 	% openafs-config --cflags pthread
> 	-DAFS_PTHREAD_ENV
> 	% openafs-config --libs pt pthread
> 	-lafsauthent -lafsrpc
>
> keywords: pt pthread ubik rx ka comerr pic static volser vl
> cmd acl auth bos budb ...
>
> This can know about "_pic", whether a given architectures supports
> or requires pic, special options to pass to the compiler to make
> compatible objects and libraries, etc.  I believe this would make
> packaging much simpler, and would also make it less necessary
> for application developers to know which libraries are needed by
> which parts of openafs.  That's going to become more important
> as things like strlcpy references in com_err, rxgk or rxk5, kerberos 5,
> etc. enter the picture.
>
> ...
>
> 					-Marcus
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>