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

René J.V. Bertin rjvbertin at gmail.com
Mon Feb 2 16:28:16 GMT 2015


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).
My problem is that cmake is apparently run even if you point to an already configured build directory. Am I mistaken on that point?

R.



More information about the KDevelop mailing list