[19550] in Kerberos_V5_Development
Re: Looking for Makefile advice if applicable
daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Wed Mar 1 00:34:47 2017
Date: Tue, 28 Feb 2017 23:34:33 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: MIT Kerberos Dev List <krbdev@mit.edu>
Message-ID: <20170301053432.GA30306@kduck.kaduk.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20170228195436.GA28781@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Tue, Feb 28, 2017 at 01:54:36PM -0600, Will Fiveash wrote:
> I'm wondering if there is a better way to achieve the following: I'm
> creating a new crypto provider for krb5 and in doing that I've created
> the src/lib/crypto/ucrypto/ subdirectory. The contents of that
> directory are similar to what is in the src/lib/crypto/openssl directory
> except that some of the cipher support is coming from source under
> src/lib/crypto/builtin like des. What I got working was to create
> src/lib/crypto/ucrypto/des and in that dir I created symlinks like
>
> des_int.h -> ../../builtin/des/des_int.h
> des_keys.c -> ../../builtin/des/des_keys.c
> destest.c -> ../../builtin/des/destest.c
> ...
>
> I am able to build the ucrypto provider this way but I'm wondering if
> there is a more refined way of doing this via the Makefile? I did play
> around with modifying the src/lib/crypto/ucrypto/des/Makefile.in
> like so:
I think this is the sort of thing that the VPATH variable is for.
So you could set VPATH = ../../builtin/des and declare dependencies
on the bare des_int.h and des_keys.c names but pull in their
contents from the original location.
-Ben
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
