CppCheck: actually generate analyzer information for markup files

Author: firewave

lib/cppcheck.cpp

@@ -693,8 +693,12 @@ unsigned int CppCheck::checkFile(const FileWithDetails& file, const std::string
                 }
                 mUnusedFunctionsCheck->parseTokens(tokenizer, mSettings);
 
-                // TODO: open file so we can set the fileinfo
+                // TODO: how to get the proper tokenlist to generate the proper hash?
+                const std::size_t hash = time(nullptr); // calculateHash(tokenizer.list, mSettings);
+                std::list<ErrorMessage> errors;
+                mAnalyzerInformation.analyzeFile(mSettings.buildDir, file.spath(), cfgname, hash, errors);
                 mAnalyzerInformation.setFileInfo("CheckUnusedFunctions", mUnusedFunctionsCheck->analyzerInfo());
+                mAnalyzerInformation.close();
             }
             return EXIT_SUCCESS;
         }

test/cli/qml_test.py

@@ -2,7 +2,6 @@
 # python3 -m pytest test-qml.py
 
 import os
-import pytest
 from testutils import cppcheck
 
 __script_dir = os.path.dirname(os.path.abspath(__file__))
@@ -53,8 +52,6 @@ def test_unused_functions_j():
     assert ret == 0, stdout
 
 
-# TODO: fillSampleData is not unused
-@pytest.mark.xfail(strict=True)
 def test_unused_functions_builddir(tmpdir):
     build_dir = os.path.join(tmpdir, 'b1')
     os.mkdir(build_dir)