On Monday December 22 2014 15:33:44 Lawrence Velázquez wrote: > Sorry, but no. Read the xcrun(1) man page. Despite its name (which you're > reading way too much into), it's intended to invoke the tools in the "active > developer directory". It's intended to let developers switch between > toolchains easily, whether those toolchains come from Xcode stable or Xcode > beta or the CLT.
What's the point then, if the traditional commands already point to the copies in the "active developer directory" ... > Instead of breaking xcrun and xcodebuild, you'd probably be better off with > judicious use of the DEVELOPER_DIR, SDKROOT, and TOOLCHAINS environment > variables. These are described in xcrun(1). As I stated before, I modified xcodebuild so that MacPorts wasn't complaining that I didn't have an Xcode install. I modified xcrun later, but the reason must have been quite similar. If I can achieve the same result with a couple of env. variables, that'd be great of course. > It's LLVM upstream that actively moved towards requiring an OS X SDK (and > thus Xcode) on Darwin. That's not really a wave I'm interested in swimming > against. I said *using* Xcode. I know full well that installing Xcode is about the only way to get the OS X SDKs, and as you must have noticed, I do have Xcode installed. Anyway, as I also said, clang-3.6 is no priority for me, esp. if it's still in beta. R _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
