On Sat, Aug 6, 2011 at 2:02 PM, dsh <daniel.hais...@googlemail.com> wrote: > Hi Jean-Sebastien, > > for which Xcode versions shall we be heading for? 4.1 or 4.2 on Lion > (I have 4.2 dev preview 5 on one of my Lion systems to develop iOS 5 > apps) and 4.0.2 on snow leopard? I would then check which would be the > min LLVM/clang version that needs to be supported.
If I remember correctly 4.0.2 didn't have all the required C++0x support (I didn't research it extensively though), but I'm pretty sure that 4.1 and 4.2 are based on LLVM 3.0+ and should work. I have Xcode 4.1 on Lion right now, but if you only manage to make it work with Xcode 4.2 that's OK with me too, I'll just upgrade to 4.2 as well :). > Shall we try to keep GCC compatibility if possible (e.g. should it be > possible to build Tuscany on platforms where there's no LLVM > distribution available)? On FreeBSD for instance it's your own > decision whether to compile the system's user-land utilities etc. > either using GCC or LLVM/clang. FreeBSD makes this possible by either > setting CC to CC=gcc or CC=clang and so on in /etc/make.conf. Maybe we > could use a similar mechanism... Yes, I'm interested in keeping compatibility with GCC for some time to run it on my EC2 and home servers, which don't have LLVM yet... Best would be to detect availability of LLVM in configure.ac and automatically point CC and CXX to it when available, and have a --with-llvm=yes/no configure option to override that if needed (like with the other configure options listed by configure --help). The configure.ac language is a little cryptic so let me know if you need help with that detection + option setup, as I've already done similar things several times. > > Concerning CMake - That has for now low priority to me I would focus > on LLVM and if that is done on CMake. > Sounds good! -- Jean-Sebastien
