Re: [cdt-dev] cmake support how to integrate the compile_commands.json p

[15 knots <fifteenknots505@xxxxxxxxx>]

Am Mi., 17. Juni 2020 um 21:09 Uhr schrieb Mark B <marco.stornelli@xxxxxxxxx>:

Il mer 17 giu 2020, 21:02 15 knots <fifteenknots505@xxxxxxxxx> ha scritto:

Hi Alexander,

Am Mi., 17. Juni 2020 um 09:31 Uhr schrieb Alexander Fedorov
<alexander.fedorov@xxxxxxxxxx>:
>
> Well, currently all these parts, such as the "server" and "front-end", are managed from the IDE.
> For example if user adds the source file - it needs to be added to json as well, and we need to guess the commands for this new unit, and for this we need to know how the surrounding units are configured.

Just *creating* a source file does not *add* it to the files that get
compiled. Cmake users must modify the CMakeLists.txt file to have the
new file compiled:

Unless you use a file glob option *.cpp in this case you don't need to modify it even if it's a discouraged approach actually.

 

Sure that will work. But then users will have to manually launch cmake every time they add or delete a source file. [1].

Unless CDT modifies the user's CMakeLists.txt and silently adds a CONFIGURE_DEPENDS. Well, the CONFIGURE_DEPENDS will give them a build-performance degradation that might be acceptable for hello-worlds. But not for projects with 1k or more source files.





[1] https://stackoverflow.com/a/34962848