Date: Thu, 21 Dec 2006 08:17:24 -0800 From: Micah <micahjon@ywave.com> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: Properly controlling CFLAGS/CXXFLAGS Message-ID: <458AB394.1000205@ywave.com> In-Reply-To: <458A0620.5020905@u.washington.edu> References: <458A0620.5020905@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
> Coming from Gentoo we were taught how to 'rice' our machines.
> Based on my experience though with FreeBSD, this is an improper
> methodology for one to use.
> I was wondering (looking at the make.conf manpage), what's the
> best way to control one's CFLAGS/CXXFLAGS. I'd prefer if only a few
> ports would have optimized compiler flags, while the rest of the system
> used a safe set of compiler flags.
> So, I was wondering what the best course of action for setting
> variables in /etc/make.conf would be? Is this proper given what I'm
> trying to accomplish:
>
> /etc/make.conf snippet:
>
> CFLAGS= -O2 -pipe
> CXXFLAGS= ${CFLAGS}
> COPTFLAGS= ${CFLAGS} -msse -msse2 -mfpmath=sse,387
>
> NO_CPU_CFLAGS="YES"
> NO_CPU_COPTFLAGS="YES"
>
> CPUTYPE?=pentium4
>
> TIA!
> - -Garrett
sysutils/portconf might allow you to do what you want. I just use the
following construct in make.conf though, and it seems to work.
.if ${.CURDIR:M*/category/port}
or
.if ${.CURDIR:M*/category/port*}
put port specific defines here
.endif
BTW, questions like this probably are best served on questions@ instead
of hackers@.
HTH,
Micah
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?458AB394.1000205>