Qt5/Mac header finding in KDevelop5 (DefinesAndIncludeManager??)

Aleix Pol aleixpol at kde.org
Thu Jun 23 10:55:13 UTC 2016

On Wed, Jun 22, 2016 at 8:23 PM, René J.V. <rjvbertin at gmail.com> wrote:
> On Wednesday June 22 2016 18:13:11 Aleix Pol wrote:
>> It's "DefinesAndIncludesManager". Missing 's'.
> Either way, I don't think that's the first place to introduce support for -iframework. The user shouldn't have to add paths that are already specified.
> What I think we need first is support for that option (and -F) as it's detected by the build system manager; `struct CMakeFile` should get a frameworkDirs member, for instance.
> I'm going to approach this from the opposite end, set a breakpoint in MakeFileResolver::processOutput where it detected a -iframework option and see how we got there. The information I added to PathResolutionResult should be read out somewhere ...
> R.

The user doesn't need to add anything, the metadata comes from
compile_commands.json. Hence our need to parse it.


More information about the KDevelop-devel mailing list