Date: Thu, 5 Oct 1995 19:12:25 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: adam@veda.is Cc: ports@freebsd.org Subject: Re: nntp dependency Message-ID: <199510060212.TAA18875@forgery.CS.Berkeley.EDU> In-Reply-To: <199510051333.NAA26157@veda.is> (message from Adam David on Thu, 5 Oct 1995 13:32:59 %2B0000 (GMT))
next in thread | previous in thread | raw e-mail | index | archive | help
* Was ctime chosen as a random executable belonging to cnews?
* Wouldn't it be better to depend on ${PREFIX}/lib/libcnews.a and
* ${PREFIX}/include/dbz.h although they are not executable? Is there
* any reason why BUILD_DEPENDS should not also be used for static
* libraries and library header files needed during the build? What is
* a suitable way of depending on both the library and the header file
* without causing the depended port to be made twice?
Yes. I don't think it makes any difference. Yes, because it uses
"which", which looks for executables only. I don't understand the
"made twice" part, and I'm sure BUILD_DEPENDS handles it fine.
* Is there an accepted convention for substituting variables such as
* ${PREFIX} into patchfiles? This port currently has /usr/local
* hardcoded at a deeper level, and I suspect there are other ports
* that suffer from the same problem.
The default do-build target will pass down PREFIX in the environment
so if you can pick it up from there, it will be fine. Just do a
"CFLAGS += -DPREFIX=${PREFIX}" or something in the Makefile.
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510060212.TAA18875>