Build fails intermittently requiring a complete rebuild; Best IDE for kdevelop
micky686 at gmail.com
Thu Mar 22 19:42:40 UTC 2018
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!
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,
> > 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
> * The usual build process is something like `cd build/ && cmake .. &&
> Running CMake directly in the source directory is probably not advisable.
> * You might want to try `cmake -GNinja .. && ninja` - it's quicker than
> and seems more reliable.
> * Using ccache can reduce the cost of repeated clean builds, at the cost
> occasional strange issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel