Do not guess include paths when we any where returned by the manager.
The IncludePathComputer was run quite frequently and is very costly. Especially for cmake projects, the build manager does a good job at finding the include paths already. Thus the up to 16s (for my KDev* session) spent in running make and interpreting its result can be saved when we instead rely on the result given by the builder. If you suddenly encounter issues with include paths that used to work, please report that on bugs.kde.org. CCMAIL: kdevelop-devel@kde.org
Showing
- languages/cpp/includepathcomputer.cpp 25 additions, 50 deletionslanguages/cpp/includepathcomputer.cpp
- languages/cpp/tests/test_cppcodegen.cpp 4 additions, 7 deletionslanguages/cpp/tests/test_cppcodegen.cpp
- languages/cpp/tests/test_specialcompletion.cpp 0 additions, 4 deletionslanguages/cpp/tests/test_specialcompletion.cpp
Loading
Please register or sign in to comment