Closed joka921 closed 2 months ago
What's the benefit of this vs using the cmake flag DONT_UPDATE_COMPILATION_INFO
?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 94.14%. Comparing base (
691439c
) to head (b3e3f3c
). Report is 3 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
2 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
@RobinTF The DDONT_UPDATE_COMPILATION_INFO flag has several disadvantages:
In summary I think that my approach makes everyone happy using the default configuration.
Since #734, QLever uses
cmake
magic to generate a fileCompilationInfo.cpp
with information about the commit hash of the current code and the compilation date. This information was then linked to each binary that uses theIndex
class, which includesServerMain
andIndexBuilderMain
as well as most of the test binaries. As a result, re-compilation took rather long even for minor code changes, which is annoying during development.This is now fixed by only linking this information only to
ServerMain
andIndexBuilderMain
. All other binaries get some default values, which is fine because they don't need this information anyway.