On Thu, Aug 02, 2001 at 10:10:25PM +0300, Heikki Korpela wrote:
> On Thu, 2 Aug 2001, Jacob Meuser wrote:
>
> > So, what's the prefered method?
> > CC ?= gcc OR
> > CC = OR
> > CC = ${CC}
>
> For the port Makefile, empty string.
>
> For a Makefile in the port's sources, CC ?= gcc for non-GNU Makefiles;
> this is for possibly feeding back patches to the developers. (If you're
> not planning to do so, you can just leave it empty; CC should also
> be provided by system Makefiles.
>
> GNU make does not support ?= - see:
>
> http://www.gnu.org/manual/make-3.79.1/make.html
>
> , but it is usually used with autoconf anyways, which typically picks
> up your CC settings with a configure script.
This is not important anyways. See make(1). Realize that command-line
settings DO override Makefile contents... and ever since we fixed make
to be posix compliant, it propagates to submakes as well.
So, you don't even need to patch the Makefile/Makefile.in.
Just pass CC=${CC} in MAKE_FLAGS/FAKE_FLAGS and be done.
We have been using this technique for quite a while... it's about the
only sane way to handle fake.
|