Date: Wed, 8 Nov 2000 21:04:19 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: andrew@ugh.net.au Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bsd.prog.mk and /usr/local/include Message-ID: <200011082104.OAA26181@usr08.primenet.com> In-Reply-To: <Pine.BSF.4.21.0011032351150.38602-100000@starbug.ugh.net.au> from "andrew@ugh.net.au" at Nov 04, 2000 12:00:50 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> What is the proper way to get the C compiler to look in ${PREFIX}/include
> for header files and ${PREFIX}/lib for libraries when using bsd.prog.mk?
>
> I can just use CFLAGS+= -I${PREFIX}/include -L${PREFIX}/lib but I suspect
> there may be a better way. grepping for -I in bsd.prog.mk didn't show up
> much however.
Depends on why you are doing it. If you are using a compiler that
is not the default compiler, and setting DESTDIR, you will have to
set it by doctoring the CC line itself, since DESTDIR will cause
your include path and library path to be overridden in this case
(I saw this while using a newer g++ for exception handling and RTTI).
If you are doing it for any other reason, setting CFLAGS for the
include path and LDFLAGS for the library path is probably the
right way to do it.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011082104.OAA26181>