On Jul 29, 2009, at 1:30 PM, Ryan Schmidt wrote:
On Jul 29, 2009, at 11:35, Toby Peterson wrote:
Setting CPP explicitly qualifies as "trying too hard". Nearly every
port in existence will use "$(CC) -E", so setting CC is sufficient.
The intended use of the CPP environment variable is to not set it
at all. :)
I changed it for gcc-4.2 only, so as to not affect current behavior
on older OS releases.
I don't think this needs to be something that varies by OS version.
If you say setting CPP is not necessary, and will not result in more
ports trying to use "cpp" or "gcc", then how about we just rename
configure.cpp to configure.rawcpp (so MacPorts sets RAWCPP and not
CPP)? We would need to handle the existing ports that use
configure.cpp carefully but long-term does this sound like an ok plan?
I'd be in favor of not setting CPP at all, and setting RAWCPP makes
even less sense considering that only a few ports use it.
If we want to make sure the configure.cpp variable is set, we can keep
it set (to "${configure.cc} -E") and just not set the environment
variable.
- Toby
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
