Skip to content
Commit 9f677552 authored by Igor Kushnir's avatar Igor Kushnir 💬
Browse files

Don't consider NoProjectIncludePathsManager ProjectSpecific

3512f890 disabled CompilerSpecific
defines and includes for QmlJS. It also started to consider
NoProjectIncludePathsManager's defines and includes ProjectSpecific in
one defines() and one includes() overload. The other overload of each
unconditionally adds NoProjectIncludePathsManager's defines and
includes. The ProjectSpecific change is unrelated and unneeded for the
fix implemented by the aforementioned commit.

Revert the ProjectSpecific change to consistently unconditionally add
NoProjectIncludePathsManager's defines and includes in all overloads.
The ProjectSpecific flag is always passed to includes() and defines(),
therefore this change does not affect KDevelop's behavior.
parent 289f106a
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment