| Summary: | KDevelop doesn't build more than one target in the Build Set | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Leandro Santiago da Silva <leandrosansilva> |
| Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | mykola.chornyi.email |
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Simple project which reproduces the bug | ||
|
Description
Leandro Santiago da Silva
2014-08-19 11:58:05 UTC
Created attachment 88332 [details]
Simple project which reproduces the bug
Open this project in KDevelop and add lala1 and lala2 targets to the build set. Try to compile the whole build set. The bug then happens.
odd that works fine for me with the project you provided. aborted sounds as if make crashed - could you check dmesg if that is the case? (In reply to Milian Wolff from comment #2) > odd that works fine for me with the project you provided. aborted sounds as > if make crashed - could you check dmesg if that is the case? Sorry for the delay... I compiled kdevelop again in a new kubuntu 14.04 installation (my previous try was in kubuntu 12.04) and the problem persists. The error is the same. There's no indication of abortion on make. No message in dmesg. The only output I have in KDevelop is, when I press F8 is: execute composite () QIODevice::setTextModeEnabled: The device is not open QIODevice::setTextModeEnabled: The device is not open kdevelop(18153)/kdevplatform (shell) KDevelop::RunController::jobDestroyed: job destroyed without emitting finished signal! @Leandro: Could you check again? Maybe with the latest KDevelop AppImage? See: https://www.kdevelop.org/download Hi everyone, I confirm that this issue can happen with Ninja builder tool I did investigation and found following in ninjabuilder.cpp ///Running the same builder twice may result in serious problems, ///so kill jobs already running on the same project This means that only one target can be build at the moment I think there should be readable feedback/output about that or build only selected target in Build Set |