Review Request 128012: Check for an existing out-of-source build dir

[Tomaz Canabrava]

I have projects/*  and builds/* and I always need to edit the config file
after configuring a project on kdevelop.
Em 25 de mai de 2016 13:20, "René J.V. Bertin" <rjvbertin at gmail.com>
escreveu:

> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/128012/
>
> On May 25th, 2016, 6 p.m. CEST, *Aleix Pol Gonzalez* wrote:
>
> So what's your use-case?
>
> Do you want to have projects/dolphin and projects/build?
>
> My use case is indeed one in which I have a work directory that holds separate source, build and possibly other directories (a temporary install directory, for instance).
>
> If I thought out-of-source build directories were that uncommon I wouldn't have proposed this patch of course. But your example is why I added a suggestion to check only for pre-configured o-o-s build directories.
>
>
> - René J.V.
>
> On May 25th, 2016, 4:48 p.m. CEST, René J.V. Bertin wrote:
> Review request for KDevelop.
> By René J.V. Bertin.
>
> *Updated May 25, 2016, 4:48 p.m.*
> *Repository: * kdevplatform
> Description
>
> When importing a new project, check if it already has a pre-existing out-of-source build directory, and propose that as the build directory in KDevelop::proposedBuildFolder().
> This is comparable to proposing to put the build folder alongside an existing src directory (but has priority over that rule).
>
> Testing
>
> Builds and behaves as expected.
>
> Diffs
>
>    - project/helper.cpp (6df9f90)
>
> View Diff <https://git.reviewboard.kde.org/r/128012/diff/>
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160525/0c7d7984/attachment.html>