Changes between Version 7 and Version 8 of UsingTheRightCompiler

Timestamp:

Apr 30, 2010, 2:47:42 AM (14 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

refinements

UsingTheRightCompiler

@@ -16 +16 @@
 or on Tiger to downgrade to gcc 3.3 to compile old software that is not compatible with gcc 4.
 
-Software by default builds using "`gcc`" and this can be a problem if the user has changed what "`gcc`" is.
+Software by default builds using "`gcc`" (or, equivalently, "`cc`") and this can be a problem if the user has changed what this is.
 On the one hand, gcc 4 may be too new to compile some very old software,
 but on the other hand gcc 3.3 is probably too old to compile a lot of modern software.
@@ -51 +51 @@
 unless that compiler doesn't work with that port for some reason.
 In that case,
-you can select a different compiler for that port by overwriting ${configure.cc} and friends,
+the maintainer can select a different compiler for that port by overwriting ${configure.cc} and friends,
 but what you probably want to do instead is overwrite the ${configure.compiler} variable,
-which sets everything for you as a group.
+which sets all the related variables for you simultaneously.
 MacPorts knows about a handful of compilers:
 
@@ -78 +78 @@
 (e.g. "apple-gcc-4.0" corresponds to the apple-gcc40 port).
 The remaining compiler names refer to compilers installed by Xcode
-(e.g. "gcc-4.0" is the gcc 4.0.1 compiler installed by Xcode
-which is the default compiler on Mac OS X 10.4 and 10.5).
+(e.g. "gcc-4.0" is the gcc 4.0.1 compiler installed by Xcode).
 Note that if you set ${configure.compiler} to a compiler provided by a MacPorts port,
-you must also declare a build dependency on that port.
+you must also declare a library dependency on that port.
 
 For the MacPorts gcc 4 compilers,
@@ -100 +99 @@
 Setting the CC, CXX and CPP environment variables at configure time
 is all that most software needs in order to use the compiler we want.
-But some ports have unusual configure scripts that don't obey these settings.
-Some ports don't have a configure phase at all.
+But some ports have unusual configure scripts that don't obey these settings,
+and some ports don't have a configure script at all.
 For such ports, it can be necessary to set the variables at build time:
 
 {{{
-build.env-append        CC=${configure.cc} \
+build.args-append       CC=${configure.cc} \
                         CXX=${configure.cxx} \
                         CPP=${configure.cpp}
@@ -113 +112 @@
 In these cases, patches are needed.
 For example, "`gcc`" or "`cc`" can be replaced with "$(CC)" in the Makefile,
-possibly in combination with setting ${build.env} as above.
+possibly in combination with setting ${build.args} as above.
 Such patches should usually be sent upstream for inclusion in the next version of the software.