03-29-2016, 04:47 PM
There must be an art to getting XcodeLegacy.sh to work reliably, since it sometimes defies logic.
I've had XcodeLegacy.sh installed in Xcode 7 for some time. I haven't been able to use any compiler but the newest one, LLVM 7, but had read that if you're running Mavericks or newer (I have El Capitan), GCC compilers won't run. Using the 10.6 SDK, however, I was able to compile some simple Cocoa test projects to run under AI CS6. Once my Xcode 7.2 was automatically upgraded to Xcode 7.3, I was unable to install XcodeLegacy at all, and went back to 7.2, renamed "Xcode72" so it wouldn't be overwritten again.
Today at work I tried running some CORE sample projects on a new cylindrical Mac Pro with Yosemite, and the GCC compiler setting worked just fine. Hah! So in drilling down into my Xcode 7.2 at home, I found the directories leading to GCC aliases, but they were all broken--if only I knew how to find where they were trying to point to. I've tried to uninstall and reinstall with the same results. Perhaps there's a permissions problem preventing them from being installed, just as I had to open permissions on my Adobe Illustrator application folder in order to build the sample plugins.
Is there a technique that's helped others coax XcodeLegacy to install reliably?
I've had XcodeLegacy.sh installed in Xcode 7 for some time. I haven't been able to use any compiler but the newest one, LLVM 7, but had read that if you're running Mavericks or newer (I have El Capitan), GCC compilers won't run. Using the 10.6 SDK, however, I was able to compile some simple Cocoa test projects to run under AI CS6. Once my Xcode 7.2 was automatically upgraded to Xcode 7.3, I was unable to install XcodeLegacy at all, and went back to 7.2, renamed "Xcode72" so it wouldn't be overwritten again.
Today at work I tried running some CORE sample projects on a new cylindrical Mac Pro with Yosemite, and the GCC compiler setting worked just fine. Hah! So in drilling down into my Xcode 7.2 at home, I found the directories leading to GCC aliases, but they were all broken--if only I knew how to find where they were trying to point to. I've tried to uninstall and reinstall with the same results. Perhaps there's a permissions problem preventing them from being installed, just as I had to open permissions on my Adobe Illustrator application folder in order to build the sample plugins.
Is there a technique that's helped others coax XcodeLegacy to install reliably?