Hello,
I’m experiencing some troubles due to a recen update of the analyzer:
Is it related to the wrapepr version ?
Is it possible to come back to an older release ?
Hi @Oodini, and thanks for sharing the issue with us,
I don’t expect running an older version of build-wrapper to fix the issue.
One known possible workaround is to avoid building in a substituted or mapped network drive, and run the build directly from the “real” drive (or the UNC path if this is a mapped network drive), then analyze using the compilation database generated from there.
Would that be possible in your setup?
The problem is that we had to create a symbolic link because of long paths in some projects using ITK/VTK, whose classes have very long names…
Another workaround was shared with the user privately to unblock the analysis.
Thanks @Oodini for taking the time to share the feedback with us. This helps us improve the product.