Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] The way of managing the build console windows

The billion dollar question is why does Configure have it's own console window. And why are there two CDT consoles (per project and global).

I have interest in unifying the CDT build console into one, the Global one. Then we can do interesting things like implement hyperlinks and such in one place and everyone benefits.


On Tue, Jan 19, 2016 at 2:15 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
Hi Karim,

can you open a bug on this issue so it can be discussed (I'm not familiar with the details myself).

Thanks for the proposed patch. However, to properly handle intellectual property, we can only accept patches using Gerrit.  Here is some info on how you can post your patch on Gerrit:



From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Ragab, Karim [Karim_Ragab@xxxxxxxxxx]
Sent: January 18, 2016 6:56 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] The way of managing the build console windows

Hi All,


Concerning managing the build console windows, the way of keeping the most recent created console always on top makes some issues.


For example this scenario:

-Create an autotools project and Build it. (the ‘Configure’ console window will be created and written to it, then the ‘CDT Build Console’ window will be created and will be the most recent created one)

-Selecting ‘Reconfigure Project’. (Nothing is displayed on the console as the ‘CDT Build Console’ window is the most recent created one – the one on top - not the ‘Configure’ one. However the ‘Configure’ console window is being updated)

-Invoking autoconf. (will create the ‘Autotools’ console window and it will be the most recent created one now)

-If selected build or clean or reconfigure project, nothing will be displayed on the console window as the ‘Autotools’ console window is now the most recent created one and other consoles will not be dispayed.


Relative issues:  CDT build console incorectly process multi-window case


I found that the above scenario issue is caused by the class, which shows the opened console (the one on top) not the one being edited.

This was a result of that patch here: Ability to have a single build console for a multi-project build, which shows clearly that this behavior was made to keep the CDT Global build console window on top for multiple projects builds.

So why can’t we just show each console that is being edited and when someone needs to show the global console then he can pin it and it will be on top?


Attached a patch to fix that issue by displaying the console window being updated except for the global console window as it just reflects the other consoles, and if needed then it can be pinned.

cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top