On Do, 2016-06-09 at 16:07 +0200, Milian Wolff wrote:
> On Donnerstag, 9. Juni 2016 13:27:26 CEST Tobias Hunger wrote:
> > On Do, 2016-06-09 at 08:43 -0400, Brad King wrote:
> > > > "includePath":
> > > > [
> > > > "/tmp/cmake-build-test/Utilities",
> > > > # <snip>
> > > > "/home/code/src/cmake/Source/CursesDialog/form"
> > > > ],
> > >
> > >
> > > Do we need some indication of whether each path is a "system" include
> > > dir?
> >
> > Having that information would not hurt, but is not really critical IMHO.
>
> I'm actually with Brad here. At least KDevelop's clang integration makes
> heavy
> use of -isystem to silence warnings etc. from stuff outside the project. We
> could hack that in ourselves by comparing an include path with the project
> root, but a better approach would be to get the info directly from CMake
> itself.
Ok, changed.
"includePath" is now reported like this:
"includePath":
[
{
"isSystem":false,
"path":"/tmp/cmake-build-test/Utilities"
},
# <snip>
]
Best Regards,
Tobias
--
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
