XCode 4.3
Jeremy Huddleston
jeremyhu at macports.org
Fri Feb 17 10:19:23 PST 2012
That's probably because sudo preserves $HOME.
On Feb 17, 2012, at 3:12 AM, Aljaž Srebrnič <a2piratesoft at gmail.com> wrote:
> Oh, and by the way, it looks like the agreement to the license is stored on a pre-user basis, so when you try to build AquaLess, for example, the build fails with "You have not agreed to the Xcode license agreements, please run xcodebuild standalone from within a Terminal window to review and agree to the Xcode license agreements." even if you have already agreed… I even tried $sudo -u macports xcodebuild; accepted the license, but it didn't stay (probably because it needs to write some file to the home directory…)
>
> 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
>
More information about the macports-dev
mailing list