GobPie now analyses files according to the compilation database instead of individual opened or saved files.
There is now a configuration file for GobPie, from which are read the relative paths from project root to:
the Goblint conf file;
the directory where the compilation database is located.
These two fields are mandatory.
The configuration file also includes a field to get the commands for building a compilation database. This feature was added because if compilation database creation is not done automatically, it is pretty annoying-confusing when the analysis does not run on the newly created files and the user should build the compilation database manually each time they create a new file (not too user-friendly). This approach is not optimal, but for now, it is better than nothing.
Instead of checking if the Goblint conf file with the name goblint.json exists in the project root, the existence of the GobPie conf file with the name gobpie.json is checked. Goblint configuration file can now be wherever - it just needs to exist somewhere in the project and its path must be specified in the gobpie conf.
The readMe is updated with the documentation of prerequisites for the project-to-be-analysed
The log4j got updated to a non-vulnerable version
There is a corresponding version of the demoproject also available
GobPie now analyses files according to the compilation database instead of individual opened or saved files.
These two fields are mandatory.
The configuration file also includes a field to get the commands for building a compilation database. This feature was added because if compilation database creation is not done automatically, it is pretty annoying-confusing when the analysis does not run on the newly created files and the user should build the compilation database manually each time they create a new file (not too user-friendly). This approach is not optimal, but for now, it is better than nothing.
Instead of checking if the Goblint conf file with the name
goblint.jsonexists in the project root, the existence of the GobPie conf file with the namegobpie.jsonis checked. Goblint configuration file can now be wherever - it just needs to exist somewhere in the project and its path must be specified in the gobpie conf.The readMe is updated with the documentation of prerequisites for the project-to-be-analysed
The log4j got updated to a non-vulnerable version
There is a corresponding version of the demoproject also available