[OpenAFS-devel] eliminating all the various copies that are done with lib*afs builds

[Neulinger, Nathan]

Changing the libafs makefiles to reference actual locations of the
source files via TOP_SRCDIR, and TOP_OBJDIR.

Actually, I think you should still be able to do that with the
libafs_tree target, but you might have to add a couple more subdirs to
what it includes.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Derrick J Brashear [mailto:shadow@dementia.org]=20
> Sent: Friday, September 06, 2002 1:57 PM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] eliminating all the various=20
> copies that are done with lib*afs builds
>=20
>=20
> On Fri, 6 Sep 2002, Neulinger, Nathan wrote:
>=20
> > I've been playing around with the idea of eliminating all=20
> (or at least
> > most) of the copies that are done as part of the afs build.=20
> I've done a
> > little bit of the patching required to accomplish this, and=20
> it does seem
> > to work cleanly.
> >
> > Seems to make the build process a little cleaner and=20
> faster, since you
> > don't have multiple copies of the source files getting copied around
> > (especially when you're changing the main .c file).
> >
> > Is this something that y'all would be interested in=20
> applying if I get it
> > finished up?
> >
> > From initial glance, it doesn't look like it would impact the
> > only_libafs_tree stuff, but I haven't dug into that real closely.
>=20
> It does have the side effect of making it impossible to ever=20
> get back to
> building a standalone kernel source blob, but I'm not sure=20
> we'll ever get
> back to that point.
>=20
> How were you doing it, analogous to how tviced builds stuff=20
> out of viced?
>=20
> -D
>=20
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20