It is not the same, but slightly related to LLVM/Clang's static analysis
tools. I use
compile_flags.txt.do in my projects like this:
redo-ifchange \
../conf/flags/common.rc \
../conf/flags/asn1.rc \
../conf/flags/crypto.rc \
../conf/flags/libpcsclite.pc.rc \
../conf/flags/tai.rc
. ../conf/flags/common.rc
. ../conf/flags/asn1.rc
. ../conf/flags/crypto.rc
. ../conf/flags/libpcsclite.pc.rc
. ../conf/flags/tai.rc
echo "$ASN1_CFLAGS $CRYPTO_CFLAGS $LIBPCSCLITE_CFLAGS $LIBTAI_CFLAGS $CFLAGS" |
tr " " "\n" | grep -v "^$" | sort | uniq
that produces compile_flags.txt that is completely enough for
clang-*/clangd and similar tools:
-D_THREAD_SAFE
-DDMALLOC
-DDMALLOC_FUNC_CHECK
-ffunction-sections
[...]
-g
-I/usr/local/include
-I/usr/local/include/PCSC
-O0
-pthread
-std=c99
-W
-Weverything
But of course it is manually created.
--
Sergey Matveev (
http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6422 AE1A 8109 E498 57EF