compile_commands.json not generated

[mrdiogodias]

Hi,
If I compile my project inside the container I don't have a compile_commands.json. However, if I compite it on my machine with nRF connect for vscode it is generated, with the ncs 1.8.0
Any idea why?

Thank you

[coderbyheart]

Can you upload a sample? I don't know what this file contains.

[coderbyheart]

Also please share the command you use to compile on your machine and the command you use with the Docker image .

[mrdiogodias]

It is generated inside the build folder. Below is a little of its content to give an idea (I converted into .txt because json is not supported here). I need it for a static analysis tool.
example.txt.
The command I used with docker:
docker run --rm -v ${PWD}:/workdir/project nordicplayground/nrfconnect-sdk:main /bin/bash -c '\ west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.8-branch && \ west update --narrow -o=--depth=1 && \ west build ccpl_mp -p always -b nrf9160_ccpl_v2ns'
In my machine I didn't use any command directly, because as I said I used the vscode extension. But what it uses is:
west build --build-dir /home/diogodias/repos/ccpl_mp/build /home/diogodias/repos/ccpl_mp --pristine --board nrf9160_ccpl_v2ns -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DBOARD_ROOT:STRING="/home/diogodias/repos/ccpl_mp"

And I if I build the asset_tracker_v2 example inside the container the file is generated... So is probably something wrong with my project?

[coderbyheart]

As far as I understand, the compile_commands.json is generated by Cmake. You should be able to pass this config option to Cmake using one-time compiler arguments when running west build.

[mrdiogodias]

It worked, thank you. Just a little strange that in my machine and with the asset_tracker_v2 inside the container I don't need to specify this in the west build command.