search for: posix&gcc

...onments than CMake. Implementing the requirement you mention seems easy enough while using toolchains where clang/clang++ works as a drop-in replacement for the platform compiler (i.e. gcc/g++ on Linux). For the general case, it looks quite tricky. The feature can be implemented for the easy case (POSIX&gcc, which, most likely, is what everybody uses) and reject it for the rest. BTW, is compiler-rt integrated in the CMake LLVM/Clang build process, or is it a separate step?

Le 22 janv. 2013 à 13:12, David Chisnall <david.chisnall at cl.cam.ac.uk> a écrit : > On 22 Jan 2013, at 12:04, Duncan Sands wrote: > >> for an out-of-tree build you can use llvm-config to get include paths and so on. >> I don't think there is any point bothering with llvm-build for this case. > > CMake works nicely for out-of-tree projects. I have an

On 22 Jan 2013, at 12:04, Duncan Sands wrote: > for an out-of-tree build you can use llvm-config to get include paths and so on. > I don't think there is any point bothering with llvm-build for this case. CMake works nicely for out-of-tree projects. I have an optimiser plugin that builds this way. I'm not sure if it's fixed now, but the autoconf builds used to not install the