Bug#560693: Does not provide to detect Clang compiler

tags 560693 fixed-upstream thanks Hello, On pirmadienis 17 Gegužė 2010 12:09:25 Michal Čihař wrote: > Modestas Vainius napsal(a): > > Hello, > > > > On penktadienis 11 Gruodis 2009 17:46:48 Michal Čihař wrote: > > > Yes it is, see . So basically there should not > > > be

Bug#560693: Does not provide to detect Clang compiler

Hi Dne Tue, 11 May 2010 22:55:59 +0300 Modestas Vainius napsal(a): > Hello, > > On penktadienis 11 Gruodis 2009 17:46:48 Michal Čihař wrote: > > Yes it is, see . So basically there should not > > be needed any changes unless you want to use some obscure features of > > t

Bug#560693: Does not provide to detect Clang compiler

Hello, On penktadienis 11 Gruodis 2009 17:46:48 Michal Čihař wrote: > Yes it is, see . So basically there should not > be needed any changes unless you want to use some obscure features of > the compiler. Upstream has asked you to test the patch: http://public.kitware.com

Bug#560693: Does not provide to detect Clang compiler

Hi Dne Fri, 11 Dec 2009 17:20:02 +0200 Modestas Vainius napsal(a): > But what's next? Just recognizing it does not provide much benefit. Clang > should be supported properly by adjusting cmake behaviour where needed. This > can only be done by a developer having enough knowledge of both cmake

Bug#560693: Does not provide to detect Clang compiler

tags 560693 upstream severity 560693 wishlist thanks Hello, On penktadienis 11 Gruodis 2009 15:32:51 Michal Čihař wrote: > Cmake currently reports Clang compiler as GCC (what is not that bad as > they are in most cases compatible), however it would be great if it > would also provide way to dist

Bug#560693: Does not provide to detect Clang compiler

Package: cmake Version: 2.8.0-5 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Cmake currently reports Clang compiler as GCC (what is not that bad as they are in most cases compatible), however it would be great if it would also provide way to distinguish these two compiler wi