80947 – Kdevelop should inform that building proces has been finished

Bug 80947 - Kdevelop should inform that building proces has been finished

Summary: Kdevelop should inform that building proces has been finished

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	kdevelop
Classification:	Applications
Component:	Output Views (show other bugs)
Version:	3.0.3
Platform:	unspecified Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	KDevelop Developers

URL:
Keywords:

Duplicates (1):	84278 (view as bug list)
Depends on:
Blocks:

Reported:	2004-05-05 10:56 UTC by Marcin Palka
Modified:	2006-02-20 05:58 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Marcin Palka 2004-05-05 10:56:38 UTC

Version:           3.0.3 (using KDE 3.2.2, Mandrake Linux Cooker i586 - Cooker)
Compiler:          gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)
OS:          Linux (i686) release 2.4.22-30mdk

Kdevelop should inform user that building proces has been finished. Currently it does not say that the compilation is already done. 

For my sample project it shows only:
>>*linking subeditpro_client (libtool) 
>>*Entering directory /home/marcin/Storage/Programming/Source/subeditpro/debug 
and after that there are no compiler processes running (verified with ps command).
It's a bit misleading to user. There should be a message like "Building finished" or something similar.

Comment 1 Jens Dagerbo 2004-05-05 23:00:01 UTC

Something is a bit buggy with the regexps of the makewidget. I think I've seen the brief view neglect to show the first or the last compile action.

I wonder if this isn't a dupe though.

Comment 2 Matt Rogers 2005-09-23 05:43:41 UTC

*** Bug 84278 has been marked as a duplicate of this bug. ***

Comment 3 Matt Rogers 2006-02-20 05:58:39 UTC

I get a "***Success***" message at the bottom of the Messages output view with the upcoming KDevelop 3.4 release. Please upgrade to a newer version of KDevelop and if you still have the problem, please reopen this bug.