Bug 384612 - Build starts from beginning using existing build dir
Summary: Build starts from beginning using existing build dir
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: CMake (show other bugs)
Version: 5.1.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-12 08:37 UTC by Gaël de Chalendar (aka Kleag)
Modified: 2022-12-10 05:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gaël de Chalendar (aka Kleag) 2017-09-12 08:37:19 UTC
Description: 
I build a large cmake based project composed of a master cmake and subprojects added with the cmake command ExternalProject_Add. for that, we use a bash script  that calls cmake and then make and make install. When something goes wrong, I open the problematic subproject in kdevelop and ask for the build from there.


    Actual Results: 
        The build of the subproject starts at 0%.

    Expected Results: 

        The build of the subproject should restart from where it was using the script (say 83%)

    Build Date & Platform: 

       Up to date KDE Neon User Edition


       It was not occurring with Kdevelop4


Project in question:
https://github.com/aymara/lima

Build script:
        The build of the subproject should restart from where it was using the script (say 83%)
Comment 1 Justin Zobel 2022-11-10 08:52:50 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-25 05:17:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-10 05:14:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!