I'm looking at the Git project in SourceTrail from a Visual Studio (Ninja) generated compile_commands.json file (via a CMakeLists.txt within the Git project).
I'm then looking at those standard functions that return size_t, such as strlen that in Linux git are (in enough cases to cause problems on Windows) then coerced into long variables.
When I hover over the strlen function in SourceTrail it is showing it as a nonindexed function with unsigned long long as the return type - which isn't standard (size_t), and doesn't reflect the return type shown if I switch to Visual Studio (size_t).
== Where does the nonindexed function return type unsigned long long come from?
What is the best method for fixing this? (the project is loaded entirley from the sanitised compile_commands.json file (swaps VS options to dashed form)
I'm looking at the Git project in SourceTrail from a Visual Studio (Ninja) generated
compile_commands.jsonfile (via aCMakeLists.txtwithin the Git project).I'm then looking at those standard functions that return
size_t, such asstrlenthat in Linux git are (in enough cases to cause problems on Windows) then coerced intolongvariables.When I hover over the
strlenfunction in SourceTrail it is showing it as a nonindexed function withunsigned long longas the return type - which isn't standard (size_t), and doesn't reflect the return type shown if I switch to Visual Studio (size_t).== Where does the nonindexed function return type
unsigned long longcome from?What is the best method for fixing this? (the project is loaded entirley from the sanitised
compile_commands.jsonfile (swaps VS options to dashed form)