Date: Mon, 10 Feb 2003 14:34:11 -0800 From: "Sam Leffler" <sam@errno.com> To: "Alfred Perlstein" <bright@mu.org>, <phk@phk.freebsd.dk> Cc: "Peter Wemm" <peter@wemm.org>, <arch@FreeBSD.ORG> Subject: Re: Indiscriminately installing all .h files in /usr/include/* Message-ID: <143501c2d154$9c3c70e0$52557f42@errno.com> References: <43624.1044915959@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> In message <20030210221501.GF88781@elvis.mu.org>, Alfred Perlstein writes:
> >* Peter Wemm <peter@wemm.org> [030210 14:09] wrote:
> >> >
> >> > If there was a way to do it via cpp defines inside the header that
would
> >> > be nice.
> >>
> >> Something like this perhaps?
> >> ^/* EXPORT_HEADER */$
> >
> >Yes, something like that. I know of one company that brackets the
> >headers with $COMPANY_PRIVATE for stuff that shouldn't be visible in
> >/usr/include. if you wind up with an empty file it isn't even installed.
>
> I would prefer labeling the stuff that should go into /usr/include,
> it shouldn't be the default to export stuff unless you ask for it.
Sticking this stuff inside include files means modifying imported files.
I'd actually prefer a mechanism like this to lurk in the Makefiles as you
can fully encapsulate requirements like the /usr/include/<dir> is different
than the source directory.
Sam
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?143501c2d154$9c3c70e0$52557f42>