Are the three main compiler flavors supported by Xcode (gcc 4.0, 4.2, and llvm) binary-compatible with one another? What kind of gotchas and corner cases should I be aware of when bringing a multi-library project up to speed with the most recent Xcode tools?
相关问题
- Xcode debugger displays incorrect values for varia
- Error building gcc 4.8.3 from source: libstdc++.so
- Image loads in simulator but not device?
- importing files from other directories in xcode
- What are the recommended GNU linker options to spe
相关文章
- xcode 4 garbage collection removed?
- Xcode: Is there a way to change line spacing (UI L
- Unable to process app at this time due to a genera
- Popover segue to static cell UITableView causes co
- “Storyboard.storyboard” could not be opened
- didBeginContact:(SKPhysicsContact *)contact not in
- gcc/g++ gives me error “CreateProcess: No such fil
- Calls that precede a function's definition can
A minor gotcha is that if you want to compile PowerPC code that will run on a G3, you must use GCC 4.0.
Clang is ABI-compatible with code generated by gcc. Clang also includes experimental support for some newer Objective-C ABIs, but compiling for the newer ABI requires flags, and generated code can be mixed with GCC-generated code anyway.