Feature request to support multiple configuration targets

[AnasKhedr]

I would be really great if the project can support multiple configurations for multiple targets for example
it can generate commands for:

• bazel build --config=binary_config //path/to/target:bin
• bazel test --config=test_config //path/to/test:bin

it would be also great if every target can support tags or additional arguments at the end, e.g.

• bazel test --config=some_config //path/to/target:bin --test_tag_filters=unit + additional options

[kiron1]

I understand the first point. This is currently not possible.

As a work around, you could use a wrapper script which calls bazel-compile-commands with your desired config+target combination and then uses jq to merge the resulting json files into one.

I don’t see what the motivation is for the second point.

[AnasKhedr]

first of all, thanks for this awesome tool
for first point, you pretty much provided the perfect solution, I didn't think of using a script to do what I want and thanks for the jq tip. I didn't know that this tool existed
for the second point, I guess you could say it's a special case for the project I'm working on, in a nutshell, all the unit tests have an addition "unit" tag and so it's useful to test all unit test from CI e.g. bazel test //project/... --test_tag_filters=unit
I was being lazy and didn't want to keep adding new tests manually since the test_suite doesn't produce compile commands

anyways I think this feature is no longer needed since my main purpose was the first point

[kiron1]

With #47 I would consider it done.

[kiron1]

@AnasKhedr what actually will better suite your use case is https://github.com/kiron1/basil-tonic. basil-tonic will listen for Bazel build events and update the compile_commands.json file in your workspace. This will work with different target + config combinations. Every Bazel build|test ... call will update the compile_commands.json with its respective settings.

[AnasKhedr]

Thanks for the update,

I actually wrote this script to do what you suggested and it's working great:

#!/bin/bash

# those are the variables you need to modify to your liking
OUTPUT_FILE="/path/compile_commands.json"
TMP_JSON_FILES_DIR="/tmp/bazel_compile_commands/"

# you can add a new target here if you wish
targets=(
    "bazel-compile-commands -v -B /usr/local/bin/bazel  -b --config=config1  --targets //path/to/project/code:mybin"
    "bazel-compile-commands -v -B /usr/local/bin/bazel  -b --config=config2 -b --test_tag_filters=tag1,tag2 --targets //path/to/project/..."
)

rm -rf $TMP_JSON_FILES_DIR
mkdir -p $TMP_JSON_FILES_DIR

rm -f $OUTPUT_FILE
touch $OUTPUT_FILE
idx=0

for target in "${targets[@]}"; do
    cmd=$target
    cmd+=" -o $TMP_JSON_FILES_DIR/compile_commands_$idx.json"
    # execute the command
    eval ${cmd}
    # merge the results
    # jq -s '[.[][]]' "$TMP_JSON_FILES_DIR/compile_commands_$idx.json" >>$OUTPUT_FILE

    idx=$((idx + 1))
done

echo "merging the results"
jq -s '[.[][]]' $TMP_JSON_FILES_DIR/compile_commands_*.json >$OUTPUT_FILE
echo "Done"