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

[Aleix Pol]

On Sat, Jan 31, 2015 at 10:12 AM, René J.V. <rjvbertin at gmail.com> wrote:
> Hi,
>
> I've noticed that the current version of KF5 kdevelop attempts to configure projects when importing them. Under what conditions does this happen, and/or how to avoid it?
>
> KDevelop <=4.7 never did this for me, and it's one reason I use it. In my workflow I usually have specific requirements on how cmake is run (env., arguments), so kdevelop doing it automatically is a waste of time at best, and a very annoying one if this is done on a project that has already been configured.
>
> NB:  given how one cannot change the cmake "extra arguments" after the importation step (skipped when importing an already configured project), I rarely do the configure step in kdevelop. Yes, I'm aware that I can edit the file in the .kdev4 folder, but in practice it's proved to be quite easy to mess that up.
>
> R.

Yes, you are correct. The cmake build directory selector needs work to
address this by adding an extra arguments field, on the KF5 branch.
It's on my TO-DO list, but if you're interested in helping, I'll be
glad to know your ideas.

Aleix