Changes between Version 2 and Version 3 of CompilerEnvironmentVariables
- Timestamp:
- Dec 8, 2019, 7:56:21 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CompilerEnvironmentVariables
v2 v3 19 19 20 20 21 == Environment alVariables ==21 == Environment Variables == 22 22 23 To a limited extent, the behavior of compilers can also be controlled with [https://en.wikipedia.org/wiki/Environment_variable environment alvariables] instead of switches.23 To a limited extent, the behavior of compilers can also be controlled with [https://en.wikipedia.org/wiki/Environment_variable environment variables] instead of switches. 24 24 ||= Switch =||= Variable =||= Affect =||= Notes =|| 25 25 || `-I` || CPATH || treated as a delimited list of paths to be added to the default system include path list || || … … 31 31 || || CC_PRINT_OPTIONS_FILE || the file to log CC_PRINT_OPTIONS output to || || 32 32 33 Using environment alvariables can alleviate some of the problems with switches.\\33 Using environment variables can alleviate some of the problems with switches.\\ 34 34 * They are less likely to be “baked in” the installed files. 35 35 * Directories in CPATH and LIBRARY_PATH are searched **after** those specified by the command line options. 36 However, an environment alvariable is no panacea.37 * Not all build systems [https://github.com/macports/macports-ports/pull/5385 respect environment alvariables].38 * Not all environment alvariables are supported on all compilers.36 However, an environment variable is no panacea. 37 * Not all build systems [https://github.com/macports/macports-ports/pull/5385 respect environment variables]. 38 * Not all environment variables are supported on all compilers. 39 39 * Setting CC_PRINT_OPTIONS causes `-v` to behave differently. For example, it breaks FindOpenMP in CMake. 40 40