Changes between Version 38 and Version 39 of PortfileRecipes

Timestamp:

May 23, 2012, 12:17:15 AM (12 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

add gcc46 gcc47 variants; reword and explain why we still default to gcc45

PortfileRecipes

@@ -298 +298 @@
 In these cases you can use `configure.compiler` to specify an alternate compiler, for example one provided by a MacPorts gcc port.
 More commonly, a port specifies such a compiler because it needs gcj or gfortran, which Apple does not provide any version of at all.
-
-On the one hand, such ports should prefer to use the newest suitable stable version of gcc they can.
-On the other hand, a user may already have an older gcc port installed and may not want to spend the time to compile a newer one right now, or may have other reasons for preferring a particular version of gcc.
+Another reason to want compiler variants is if the software installs a library, or uses a library built with a different gcc.
+Subtle and difficult-to-find errors can occur if a library and the program using it are not both compiled with the same compiler.
+
+So on the one hand, all such ports should default to using a particular common version of gcc; the version we are currently using as the default version in MacPorts is gcc45.
+On the other hand, a user may want to use a different gcc version.
 Therefore, ports that need to use a gcc port, but aren't picky about exactly which one, are encouraged to offer variants:
 
 {{{
-variant gcc43 conflicts gcc44 gcc45 description {Compile with gcc 4.3} {
+variant gcc43 conflicts gcc44 gcc45 gcc46 gcc47 description {Compile with gcc 4.3} {
     configure.compiler macports-gcc-4.3
     depends_lib-append port:gcc43
 }
 
-variant gcc44 conflicts gcc43 gcc45 description {Compile with gcc 4.4} {
+variant gcc44 conflicts gcc43 gcc45 gcc46 gcc47 description {Compile with gcc 4.4} {
     configure.compiler macports-gcc-4.4
     depends_lib-append port:gcc44
 }
 
-variant gcc45 conflicts gcc43 gcc44 description {Compile with gcc 4.5} {
+variant gcc45 conflicts gcc43 gcc44 gcc46 gcc47 description {Compile with gcc 4.5} {
     configure.compiler macports-gcc-4.5
     depends_lib-append port:gcc45
 }
 
-if {![variant_isset gcc43] && ![variant_isset gcc44] && ![variant_isset gcc45]} {
+variant gcc46 conflicts gcc43 gcc44 gcc45 gcc47 description {Compile with gcc 4.6} {
+    configure.compiler macports-gcc-4.6
+    depends_lib-append port:gcc46
+}
+
+variant gcc47 conflicts gcc43 gcc44 gcc45 gcc46  description {Compile with gcc 4.7} {
+    configure.compiler macports-gcc-4.7
+    depends_lib-append port:gcc47
+}
+
+if {![variant_isset gcc43] && ![variant_isset gcc44] && ![variant_isset gcc45] && ![variant_isset gcc46] && ![variant_isset gcc47]} {
     default_variants +gcc45
 }
 }}}
 
-Note that the variants are all marked as conflicting with one another, and that the newest one is chosen by default if the user has not picked one.
+Note that the variants are all marked as conflicting with one another, and that one is chosen by default if the user has not picked one.
 Note also that the compiler dependencies are library dependencies because programs compiled using these compilers will generally end up linked to at least one of the compiler's libraries (i.e. libgcc_s.dylib, libgfortran.dylib, etc.).
 
@@ -337 +349 @@
 }
 }}}
-
-Another reason to want compiler variants is if the software installs a library, or uses a library built with a different gcc.
-Subtle and difficult-to-find errors can occur if a library and the program using it are not both compiled with the same compiler.
-