[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 293750] <wrong-target> when creating cmake test
From:       Andre Stein <andre.stein () rwth-aachen ! de>
Date:       2012-09-27 7:03:56
Message-ID: bug-293750-40295-0OJCxBZh7z () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=293750

--- Comment #7 from Andre Stein <andre.stein@rwth-aachen.de> ---
What about this idea: Cmake allows to generate a json file
(compile_commands.json) which contains all source files along its build command
in a JSON array:

[
{
  "directory":
"/home/stone/Documents/stone-files/steinsoft/projects/android/rockfall/src/jni/build",
  "command": "/usr/bin/c++     -pedantic -Wall
-I/home/stone/Documents/stone-files/steinsoft/projects/android/rockfall/src/jni/rockfall
-I/home/stone/Documents/stone-files/steinsoft/projects/android/rockfall/src/jni/inc
-I/usr/include/irrlicht    -o CMakeFiles/rockfall.dir/unix/main.cpp.o -c
/home/stone/Documents/stone-files/steinsoft/projects/android/rockfall/src/jni/unix/main.cpp",
  "file":
"/home/stone/Documents/stone-files/steinsoft/projects/android/rockfall/src/jni/unix/main.cpp"
},
...
]

The file will be automatically generated when
-DCMAKE_EXPORT_COMPILE_COMMANDS=on is specified during cmake configuration.
This way we could ask the build system itself anytime the cmake parser fails to
get all information needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]