Is it possible to use iOS7 SDK and still compile in llvm-gcc-4.2?
If you want to compile your whole app using llvm-gcc-4.2: Probably not. I haven't checked this myself, but the iOS 7 headers would only need to add a single dependency on a clang feature missing in llvm-gcc-4.2 and you're swimming in compile errors. You may be able to hack your way through them, but it would likely be easier (not to mention more future-proof) to suck it up and upgrade to clang.
If you only need to compile some of your app using llvm-gcc-4.2: Sure, as long as you don't need to import any iOS 7 headers in the parts that you build with llvm-gcc-4.2.
You could try moving the problematic bits off to a static library, compiling that with gcc, then linking in to the final app, built with clang. You won't be able to target 64-bit, as llvm-gcc-4.2 doesn't can't generate armv8 code, but it should work otherwise.
One caveat: If your static lib uses C++, there may be some problems due to ABI and std library differences. But those are solvable problems, at least.
clang
? – Lattaclang
? I think your only route is to go back to Xcode 4. – LattaCC
flag, as described in this post under (2). There may be a few (or many) flags that Xcode sets by default which are not supported by GCC. In this case, you'll probably see a warning in the build log... I currently don't have the possibility to test it myself. – Essequiboclang
doesn't support the__builtin
SSE instructions, that's how I arrived at this question. We used to usellvm-gcc
which was previous bundled with Xcode. – Roseliaroselin