Changes between Version 73 and Version 74 of PortfileRecipes

Timestamp:

Aug 27, 2013, 3:35:22 PM (11 years ago)

Author:

larryv (Lawrence Velázquez)

Comment:

no need to point out revision

PortfileRecipes

@@ -373 +373 @@
 If a certain compiler won't build your port, blacklist it, and MacPorts will select the next-best compiler.
 
-If your port works with clang but not llvm-gcc-4.2, do this:
-
+If your port does not build with LLVM-GCC, blacklist it:
 {{{
 compiler.blacklist *llvm-gcc-4.2
 }}}
-
-If your port works with llvm-gcc-4.2 but not clang, do this:
-
+This will prevent MacPorts from using either Xcode’s LLVM-GCC or MacPorts’.
+Similarly, if your port does not build with Clang:
 {{{
 compiler.blacklist *clang*
 }}}
-
-Note that above examples only work as of r104174 (which is in MacPorts 2.2), because that commit added support for globs being used to match patterns in the compiler name. For an example of how these globs work, the first example above will also match macports-llvm-gcc-4.2, and the second example will also match macports-clang-*.
+As of MacPorts 2.2, the elements of `compiler.blacklist` are treated as
+patterns for [http://www.tcl.tk/man/tcl8.4/TclCmd/string.htm#M34 string matching].
+See UsingTheRightCompiler for a list of available compiler values.
 
 If your port works with neither clang nor llvm-gcc-4.2, the fallback will be to gcc-4.2 (provided by the apple-gcc-4.2 port if it's not available).  It is becoming increasingly important that ports build successfully with clang since it has been the default compiler since Xcode 4.2, and Apple no longer supports the use of gcc.