Support external builds
At the moment Klever Core assumes users provide sources and some options for building their software internally. This can be reasonable and can be established for some projects like the Linux kernel but for other ones this can be an obstacle. That's why I suppose to develop a special tool for intercepting build information required for following verification objects generation and to support its output within Klever Core (although this tool can be useful not only for verification purposes I would not like to spend any my time for making it useful in a more general case, so it will be incorporated within Klever). In particular this will allow to avoid very resource consuming preparing of sources during validation based on Git commits.
#2 Updated by Evgeny Novikov over 1 year ago
Also I and Ilja Zakharov suggest to try to get rid of all compiler options except ones used for preprocessing (input and output files will be obtained anyway). It seems that we do need just the latter while other options can just confuse CIF based on GCC 4.6 when another compiler version is used for building.