[1328] in Kerberos_V5_Development
Re: sub-packages of krb5 for autoconf purposes
daemon@ATHENA.MIT.EDU (Tom Yu)
Mon Jun 17 20:08:44 1996
Date: Mon, 17 Jun 1996 20:08:12 -0400
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: raeburn@cygnus.com, tlyu@MIT.EDU, krbdev@MIT.EDU
From: Tom Yu <tlyu@MIT.EDU>
In-Reply-To: <9606171608.AA28161@DUN-DUN-NOODLES.MIT.EDU>
After discussion with Barry and Ted earlier today, I propose the
following:
* Have a single top-level configure script for the entire krb5 tree.
* Either hardcode the BUILDTOP variable in each Makefile.in or modify
AC_OUTPUT to calculate it relative to the target directory of the
configure script; i.e. if the configure.in has
"AC_OUTPUT(Makefile util/Makefile)" then BUILDTOP in util/Makefile
will be "..", and any directories with their own configure scripts
have a BUILDTOP value which is also calculated relative to their
configure scripts. Either method is acceptable if we're configuring
the majority of the krb5 tree from a single configure script. My
likely implementation is to begin with BUILDTOP set explicitly in each
Makefile.in
* If packages need to be broken out later, have their Makefile.ins be
capable of being configured by a local configure script. This allows,
say appl/telnet to be broken out into its own package that will not
look for the krb5 libs in the build tree.
* Configure util/berk_db separately (using AC_CONFIG_SUBDIRS) as it
will be a drop-in package that we use. Not certain whether we want to
configure other stuff in util separately.
Any comments? I will likely be making a branch to do this hacking as
it will cause much breakage if I keep it on the mainline for too much
longer.
---Tom
