Date: Thu, 14 Sep 2000 01:25:55 +0100 From: Paul Richards <paul@originative.co.uk> To: Peter Wemm <peter@netplex.com.au> Cc: John Baldwin <jhb@pike.osd.bsdi.com>, "Steven E. Ames" <steve@virtual-voodoo.com>, Gregory Neil Shapiro <gshapiro@gshapiro.net>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sendmail Makefile Message-ID: <39C01B13.2E19971@originative.co.uk> References: <200009132356.e8DNuSG96781@netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote:
>
> Paul Richards wrote:
> > John Baldwin wrote:
> > >
> >
> > > Then you could have things like:
> > >
> > > .ifdef(SENDMAIL_USE_SASL)
> > > SENDMAIL_CFLAGS+=-I/usr/local/include -DSASL
> > > ...
> > > .endif
> > >
> > > If you wanted to have shortcuts for common extensions. You could stick
> > > these in either sendmail's Makefile or make.conf. Probably in sendmail's
> > > Makefile though.
> >
> > More generic would be to add
> >
> > .ifdef(USE_SASL)
> > CFLAGS+=-DSASL -I/usr/local/include/sasl
> > LDADD+=-L/usr/local/lib -lsasl
> > .endif
> >
> > to the mk file so that other applications will use SASL if USE_SASL is
> > set in make.conf
> >
> > Paul Richards
> > FreeBSD Services Ltd
>
> Except we aren't meant to be hardcoding the paths.
> eg: /opt/sasl/{include,lib} is supposed to be supported. The build has
> no business hardcoding /usr/local in it. Yes, I know there are some places
True, the question is then how tied to the ports system should it be?
The following would work.
.ifdef(USE_SASL)
CFLAGS+=-DSASL -I${LOCALBASE}/include/sasl
LDADD+=-L${LOCALBASE}/lib -lsasl
.endif
but that requires LOCALBASE to be visible to the base build system which
currently it isn't.
Paul Richards
FreeBSD Services Ltd
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C01B13.2E19971>