| 42 | | Note the above is also exactly what you should do with clang, to inform it what SDK to use. Macports clang builds in particular rely on this as they, like GCC< cannot assume any specific SDK location that the user will have installed. |
| | 42 | Note the above is also exactly what you should also do with clang, to inform it what SDK to use. Macports clang ports in particular rely on this as they, like GCC, cannot assume any specific SDK location that the user will have installed. |
| | 43 | |
| | 44 | Also note whenever macports always sets SDKROOOT during builds, so whenever it uses its own GCC or clang ports (or Xcode clang for that matter) it controls the SDK used via the exact same mechanisms as above. |
