On 4 Oct 2013, at 9:45, Ash Qin wrote:

>> Shouldn't need an environment variable. Xcodebuild is directed to use 
>> the system's llvm-gcc
>
> I had tried already without ccache (and a clean build directory). What
> I hadn't tried though was not defining CXX and CC variables to LLVM.
>
> Surprisingly, I am able to compile the viewer now despite the
> deceptive message that autobuild is now using Clang. The confusing
> thing is that I can point the CXX and CC variables to the exact same
> compilers xcode is using and still get the exact same failure.
>
> This sort of behaviour leaves me a little miffed. Being that I would
> really like to use ccache in my work, would you happen to know of a
> way to tell xcode to use ccache + llvm in Second life's compilation
> process?

You might try altering the Xcode command line toolchain using xcrun to 
point to ccache instead
of the sdk's llvm. 'man xcrun' for some cryptic info on how to do so.

>> (just won't work on Xcode5, which you aren't using anyway, because 
>> Apple symlinked "llvm-gcc" to clang. -_-)
>
> So, one could get xcode5 working by just changing the symlink to the
> right compiler?

Unfortunately, no. I've been hacking at Xcode5 for a couple months now 
trying to get it to
build the viewer reliably using llvm-gcc, but it just doesn't wanna do 
it. You need to add
a compiler plugin for it, (which I have 
https://bitbucket.org/cinderblocks/xcode-compiler-plugins/wiki/Home )
and then modify the toolchain, correcting the symlink and pointing to 
all the right tools,
and then just based on the changes they made in Xcode5 there's some 
changes that have to be
made to the viewer itself anyways. I've given up on trying to force 
Xcode5 to play nice with
the viewer in it's current state and am trying to  get it to build under 
clang now for OPEN-190.

-- 
Cinder
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to