[90028] branches/release_2_0/base

[James Berry]

On Feb 20, 2012, at 1:49 AM, Joshua Root wrote:

> On 2012-2-20 19:32 , Dan Ports wrote:
>> On Mon, Feb 20, 2012 at 05:48:55PM +1100, Joshua Root wrote:
>>> On 2012-2-20 11:14 , jberry at macports.org wrote:
>>>> Use xcrun -find to find xcode compiler if it's not found in /usr/bin.
>>> 
>>> I deliberately didn't merge these, and the changes in r90031, in order
>>> to minimise the changes made on the stable branch. I'd really rather
>>> both merges were reverted. Every line of code that's changed means more
>>> delay before we can do an Xcode 4.3 compatible release and a greater
>>> likelihood of something going horribly wrong.
>> 
>> Does that mean we'll have to require people to have both Xcode and the
>> command-line tools package installed?
> 
> Yes, that seems the best way to avoid future problems if the compiler
> paths inside developer_dir change again. We require other stuff in
> /usr/bin anyway, like make.

Much as I'd like to be able to avoid having to require the stand-alone tools installer, I agree with Joshua that it's going to be hard to dispense with for now. We could get quite a way with xcrun -find, and could likely even successfully use it for tools like Make, but I think getting there is not a short term solution. We have a stable and well-known solution at present, in the stand-alone tools installer.

For tools that _are_ only in the develoer_dir, I think that using xcrun -find is a better solution than hard-coding paths into the Xcode binary: we're better off asking Xcode where those things are than trying to sneak around its back to find them.

James