--threads flag doesn't seem to be used.

[Icantjuddle]

I passed --threads=30 but htop and ps -T -p seem to show only a single thread running. Is this expected?

[Waqar144]

Yes.

I have a multiprocess script that is not public, will publish it soon.

[Icantjuddle]

Thanks @Waqar144, much appreciated!

[Icantjuddle]

@Waqar144 is the general idea to split the compile_commands.json into individual documents and run on each on them separately and point them to the same data dir?

[Waqar144]

@Icantjuddle yes. But things are a bit more complicated when it comes to writing out to the output folder. The script lives here if you want to try: https://github.com/KDAB/codebrowser/blob/master/scripts/runner.py

[Icantjuddle]

Sounds good, giving it a try; thanks for pushing it!

[Icantjuddle]

It mostly worked, the one issue I had was that there were a few files that seemed to be indexed repeatedly despite only showing up once in the compile_commands.json file.

[ogoffart]

But things are a bit more complicated when it comes to writing out to the output folder

I just make a comment to #88 (comment) with some ideas on how to improve things in that respect.

[Waqar144]

@Icantjuddle please try with latest master, a critical patch to make the runner script work correctly was missing. Should also fix the build issue you had.

[Icantjuddle]

Thanks, build is fixed, I'm still having some issues with duplicate entries in the fileIndex but a sort <fileIndex| uniq | sponge fileIndex seems to fix the issues.

Interestingly, only headers end up with duplicate entries, even though I've verified that there are not duplicates in the compile_commands.json.

[Waqar144]

I'm still having some issues with duplicate entries in the fileIndex

That is expected as multiple processes may end up appending to the file. It is easy to fix, we just need to append to a different file for each process and combine everything at the end.

Interestingly, only headers end up with duplicate entries, even though I've verified that there are not duplicates in the compile_commands.json

Compile commands only contains entries for .cpp files, header files are processed as a result of parsing a .cpp file and two cpp files can have similar headers which is why there are duplicate entries for headers only.

[Icantjuddle]

Interestingly, only headers end up with duplicate entries, even though I've verified that there are not duplicates in the compile_commands.json

Compile commands only contains entries for .cpp files, header files are processed as a result of parsing a .cpp file and two cpp files can have similar headers which is why there are duplicate entries for headers only.

I do have entries for headers in my compile_commands.json since it helps with header only libraries when used with language servers.

Thank you for all your help with this!