importing a cmake project into KF5 kdevelop starts a cmake configure?

[Aleix Pol]

On Mon, Feb 2, 2015 at 5:41 PM, Milian Wolff <mail at milianw.de> wrote:
> On Monday 02 February 2015 17:34:20 Aleix Pol wrote:
>> On Mon, Feb 2, 2015 at 5:28 PM, René J.V. <rjvbertin at gmail.com> wrote:
>> > On Monday February 02 2015 17:21:30 Aleix Pol wrote:
>> >> It's the intended behavior. Now it will use cmake to generate the
>> >> project metadata instead of processing the cmake files ourselves. The
>> >> need of a build directory is a collateral damage of that change.
>> >
>> > The issue is not that a build directory is needed. That was always the
>> > case, AFAIK (even if things worked fine without).
>> It worked without, so it wasn't required. That's what I meant.
>>
>> > My problem is that cmake is apparently run even if you point to an already
>> > configured build directory. Am I mistaken on that point?
>> If that happens, then it's a bug to solve. Please report it and I'll
>> look into it.
>
> Isn't it required nowadays to ensure we get the compile_commands.json file?
> I.e. we need to rerun cmake with the proper generator set?

Yes.
The generator isn't related, just run cmake. Also that's fine, as long
as we do it in the right directory.

Aleix