Build fails intermittently requiring a complete rebuild; Best IDE for kdevelop

[Miljenko Jakovljevic]

Hi,
using ccache with ninja is really the way to go. On my system it reduces
compilation time on a second build from 15 min to 3.8 s (in case of a
change in a single file).
Thank you very much!
Miljenko

On Wed, Mar 21, 2018 at 1:29 AM, Francis Herne <mail at flherne.uk> wrote:

> On Tuesday, 20 March 2018 20:04:24 GMT Miljenko Jakovljevic wrote:
> > Using kdevelop to develop kdevelop seems not to work on my system,
> because
> > the system recognizes that there is already a running instance, when one
> > tries to execute the modified kdevelop instance from the IDE.
>
> This can be solved by using `kdevelop --ps` to launch KDevelop, or
>  `kdevelop -s some_existing_session`.
>
> I'm not familiar with the build problem, but some comments on what you
> posted:
>
>  * The usual build process is something like `cd build/ && cmake .. &&
> make`.
> Running  CMake directly in the source directory is probably not advisable.
>
>  * You might want to try `cmake -GNinja ..  && ninja` - it's quicker than
> Make
> and seems more reliable.
>
>  * Using ccache can reduce the cost of repeated clean builds, at the cost
> of
> occasional strange issues.
>
> -Francis
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20180322/9078e907/attachment.html>