at present there's not a usable test-suite (although using the resulting tools to build GCC/LLVM is a fairly good test).See the cmake documentation for the version you're using. (but note that, unlike autoconf-based builds, I've not found a way to retrieve the command line used to configure the package, so files can be a useful record). You can set these things on the cmake invocation line likeĬmake -DCMAKE_C_COMPILER=/path/to/compiler. GCC-5.3 works fine and can be built using the default XCode toolchain.Ĭmake -C /path/to/script/file.cmake /path/to/sourceĮxample for 10.6 - you will need to modify this as relevant to your case.
XTOOLS OSX CODE
The branch islanding code has been almost completely re-written and it now supports multiple code sections (which GCC emits) and works for larger binaries (e.g.This is a heavily modified merge of the XCode 3.2.6 ppc support + my own additions to re-introduce ppc64.This is the same approach as used for other Darwin/OS X toolchain content (i.e.I wanted to avoid a clash with the build stuff contained in the original sources.The principal changes common to all versions are: Several stub libraries used when support is needed on older systems. Ld64 providing the static linker and some test utils. Problem reports should be filed to Please do not file problem reports for this code to Apple.Ĭctools providing as, nm, ar, ranlib, strip, etc. This is code has been modified, although based on the posted sources. This is a project that collects together several Open Source sub-projects from the Darwin (OS X) opensource repository ( )
0 kommentar(er)
