Date: Thu, 10 Aug 2006 22:33:51 +0200 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: Scot Hetzel <swhetzel@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: ports without configure do not receive CC Message-ID: <44DB982F.8030102@gmx.de> In-Reply-To: <790a9fff0608101328j533ca925k8f147f0c9ce80687@mail.gmail.com> References: <44DB5692.6040005@gmx.de> <20060810214516.7e0ff056@localhost> <44DB72FC.8010009@gmx.de> <20060810224838.639c57e8@localhost> <44DB87FA.4020505@gmx.de> <20060810234844.107d0871@localhost> <790a9fff0608101328j533ca925k8f147f0c9ce80687@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Scot Hetzel wrote:
> On 8/10/06, Stanislav Sedov <ssedov@mbsd.msk.ru> wrote:
>> On Thu, 10 Aug 2006 21:24:42 +0200
>> "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> mentioned:
>> > That leads to no end of problems if you have different settings for
>> different ports,
>> > because a port gets its specific settings and will later override
>> them with the
>> > settings that are set for all ports.
>>
>> You can use
>> .if ${CURDIR:M*usr/ports/CATEGORY/PORTNAME/*}
>> CC=XXX
>> .endif
>>
>> like construction to support this.
>>
> Or use the sysutils/portconf port, and then place your port specific
> variables in the /usr/local/etc/port.conf file, no need to clutter
> /etc/make.conf.
>
> CATEGORY/PORTNAME*: CC=XXX
> editors/openoffice*: WITH_TTF_BYTECODE_ENABLED
>
> Scot
Portconf wouldn't work on my system, because the location /usr/ports is hard coded,
and that's only a link on my system. I'm using buildflags, because that is a lot
more flexible.
Anyway, it's a fact that normally a port gets CC from the ports framework. And if
a port doesn't have a configure target it will not get it from there. That this
doesn't actually have an effect for 'most' people doesn't mean that it is not a problem.
I think CC and CXX should generally go into MAKE_ENV.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44DB982F.8030102>