Output compile_commands.json

[oraqlle]

Does Poac support outputting the compile_commands.json file?

[ken-matsui]

@oraqlle No

[oraqlle]

@ken-matsui Is there something similar that can be used?

[ken-matsui]

@oraqlle Poac directly outputs ninja.build (this should have been build.ninja though). This might be similar to compile_commands.json.

[oraqlle]

I look into it.

[oraqlle]

So the ninja.build cannot be used as a compilation database but ninja can use it to generate one. I created a very simple script to generate it quickly. In the future it would be awesome if this was automatically generated.

# makedb.sh

#! /usr/bin/bash

[ -d "poac-out/debug" ] && ninja -C ./poac-out/debug -f ninja.build -t compdb > ./poac-out/debug/compile_commands.json
[ -d "poac-out/release" ] && ninja -C ./poac-out/release -f ninja.build -t compdb > ./poac-out/release/compile_commands.json

[ken-matsui]

@oraqlle Should we generate the compilation database every time we build? Or do we just need it when we want? I'm going to implement building the db every time.

[ken-matsui]

@oraqlle I implemented: #767

[oraqlle]

Awesome, I'll give it a go.

[oraqlle]

Output database works but it appears to use unnecessary slashes (\) on Linux for paths. I imagine this is because Windows uses \ as a path separator which needs to be escaped in the string.