Changes between Version 25 and Version 26 of UsingTheRightCompiler


Ignore:
Timestamp:
Aug 26, 2013, 4:55:06 PM (11 years ago)
Author:
cooljeanius (Eric Gallager)
Comment:

Add information about C++ runtimes based on ​https://lists.macosforge.org/pipermail/macports-dev/2013-August/024044.html

Legend:

Unmodified
Added
Removed
Modified

  • UsingTheRightCompiler

    v25 v26  
    128128you must also declare a library dependency on that port.
    129129
     130=== C++ ===
     131One thing to be aware of when choosing which compiler to use is that different
     132compilers use different C++ runtimes:
     133
     134||= Compiler =||= C++ runtime used =||
     135|| gcc-* || host libstdc++ ||
     136|| *llvm-gcc-4.2 || host libstdc++ ||
     137|| apple-gcc-* || host libstdc++ ||
     138|| macports-gcc-* || MP libstdc++ ||
     139|| dragonegg-* || MP libstdc++ ||
     140|| clang < 163 || host libstdc++ ||
     141|| clang >= 163 || host libstdc++ or host libc++ ||
     142|| macports-clang-* || host libstdc++ or host libc++ ||
     143Be careful about mixing different C++ runtimes, as there are incompatibilities
     144between them that can lead to problems.
     145
     146=== Fortran ===
    130147For the MacPorts gcc 4 compilers,
    131148additional environment variables FC, F77 and F90 are set to the path of the Fortran compiler.
    132149These variables are not set for the other compilers because they do not include a Fortran compiler.
     150Note if that you are developing a port that uses Fortran, there is a [wiki:PortfileRecipes#fortran Fortran PortfileRecipe]
     151that you can use to simplify the usage of Fortran in your port.
    133152
    134153== Ports with nonstandard or nonexistent configure scripts == #nonstandard-ports