XCode 4.3

[James Berry]

On Feb 17, 2012, at 3:18 AM, Aljaž Srebrnič wrote:

> Also, is it only me that got clang in /usr/bin and not in /Applications/Xcode.app/Contents/Developer/usr/bin?
> All of the ports fail to build because they go look there…

xcrun -find clang gives:

	/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang

(and this is what is being found/used by port configure if clang is chosen)

James

> 
> Aljaž Srebrnič
> -- --
> My public key:  http://bit.ly/g5pw_pubkey
> 
> On 17/feb/2012, at 09:39, Joshua Root wrote:
> 
>> On 2012-2-17 18:45 , Jeremy Huddleston wrote:
>>> 
>>> Also, another thing to note is that the command line tools + SDK are
>>> available as a separate download.  If you don't need any parts of XCode
>>> itself, you can probably get by with just installing these bits, but I
>>> wouldn't recommend it for the casual MP user since many pieces of
>>> MacPorts assume you have a /Developer dir somewhere and quite a bit of
>>> logic is based on determining which version of XCode is installed.
>> 
>> In light of this and the changing developer_dir, maybe it would be a
>> better idea to move back to using tools in /usr/bin when possible. The
>> only reason we started using compilers in /Developer/usr/bin is that
>> llvm-gcc-4.2 wasn't installed in /usr/bin on Leopard.
>> 
>> - Josh
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev