Date: Wed, 15 May 2002 11:17:06 +0300 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: Bruce Evans <bde@zeta.org.au> Cc: "David O'Brien" <obrien@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: make includes Message-ID: <20020515081706.GH78035@sunbay.com> In-Reply-To: <20020515161610.U7103-100000@gamplex.bde.org> References: <20020514211757.A37033@dragon.nuxi.com> <20020515161610.U7103-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--54u2kuW9sGWg/X+X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, May 15, 2002 at 05:05:02PM +1000, Bruce Evans wrote:
> On Tue, 14 May 2002, David O'Brien wrote:
>=20
> > On Wed, May 15, 2002 at 12:38:49PM +1000, Bruce Evans wrote:
> > > > I really do not like this change, please return things such that the
> > > > long-ingraned "cd /usr/src ; make includes".
> > >
> > > I planned to fix this by changing "make includes" to print
> > > "Unwarranted chumminess with implementation".
> >
> > What is your perfered way to get the results of
> > (cd /usr/src ; make includes) ?
>=20
> I prefer not to do this. There are simpler methods to get broken
> headers, starting with rm -rf :). I prefer everyone to use (documented)
> user-level targets like "world" and "install" for installing includes,
> since it would be difficult to make the includes target safe for general
> use. I don't know what it really useful for.
>=20
It's now more useful (incsinstall) than before, for developers. Imagine
you've modified the include file foo.h and want to try if "bar" compiles
with it. As incsinstall now works on per-makefile level, you can just
install this particular include (or group of related includes), and then
just cd to bar's directory, and try to make it. It is also useful as a
standard target so we don't forget to install some includes (which might
be needed to build libraries), like we did before.
(Of course, if the header is local, one might use -I${.CURDIR}, as many
bsd.lib.mk makefiles currently do. We can now drop these or similar
lines (see libbz2/Makefile for example), but I think they are still
useful in at least "developer" mode.
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
--54u2kuW9sGWg/X+X
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE84hmCUkv4P6juNwoRAvSxAJ4+51L2vewIgaOgGacUO0cLXAcHdACeOYyA
BcDrTL0847h5CdhxzGY12Yg=
=g6yY
-----END PGP SIGNATURE-----
--54u2kuW9sGWg/X+X--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020515081706.GH78035>