Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

In my case SOONG_GEN_COMPDB exists (android 10), but following the instructions here did not generate the json file, unless you actually proceed with a full build (i.e., make nothing didn't produce the

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

Hi Dan. It looks like the option SOONG_GEN_COMPDB is not available in Pie branches. Perhaps it was added later. I wish to make use of this option. Will it be safe to use soong from master branch with Pie source code ? Were any breaking changes made in soong since Pie was branched out ? On

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

thanks, I've tried *compiledb-aosp.sh* in android-9.0.0_r34, but failed. here is the out put alex@alex-pc:~/code-reviww/aosp$ ./aosp-compdb.sh # Loading build env # Configuring x86_64 build # Chosen module: bionic/libc # Generating compilation database file

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

some module like frameworks/av is really hard to convert to Android.bp. In android-9.0.0_r34 , SOONG_GEN_COMPDB can't use directly, I need add related file to aosp soong module, then recompile soong, then I can SOONG_GEN_COMPDB, but the generated compile_commands is really big, like 83M.

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

An alternative option would be compiledb tool ( https://github.com/nickdiego/compiledb), which is able to parse compile commands from a build log. Some years ago I've been able to parse compilation database from some AOSP modules using a similar approach. On Mon, Mar 18, 2019, 13:18 'Dan

Re: [android-building] how to get compile_commands.json by mma or mm from android.mk in aosp project of android 9

The ninja compilation database support doesn't work very well for our ninja files due to kati using a rule per command. This upstream ninja feature request may help, but that's assuming that whatever is parsing the compdb files can understand the raw rules (which is usually a bash script, not just