Re: [cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

2016-08-26 Thread Brad King
On 08/26/2016 10:49 AM, Tobias Hunger wrote: > CMake used to break C++ projects in its CodeBlocks generator. Now it > probably breaks C projects. > > I think the approach is wrong: C and C++ includes should never get > concatenated. Please consider to report compiler flags/include > paths/defines

Re: [cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

2016-08-26 Thread Tobias Hunger
Hello CMake developers, CMake used to break C++ projects in its CodeBlocks generator. Now it probably breaks C projects. I think the approach is wrong: C and C++ includes should never get concatenated. Please consider to report compiler flags/include paths/defines by language. You might want to

Re: [cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

2016-08-26 Thread Brad King
On 08/25/2016 02:54 PM, Kevin Ottens wrote: > When using the Clang Code Model in QtCreator, it turned out that having > the C system include dirs can make it report false positives for most > uses on the STL. This is due to the order the Clang Code Model looks at > the include directories and some

[cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

2016-08-25 Thread Kevin Ottens
Hello, When using the Clang Code Model in QtCreator, it turned out that having the C system include dirs can make it report false positives for most uses on the STL. This is due to the order the Clang Code Model looks at the include directories and some C includes in /usr/include could be