Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Repetition of the CDT Global Build Console When Using The CDT CBuildConsole Extension

On 03/23/2011 05:19 PM, Andrew Gvozdev wrote:
 >From the code I see that CDT allows for multiple BuildConsoleManager-s
managed by CUIPlugin and each one creates Global Build Console. It
appears there was assumption that there is just one manager (as it would
be usual case). My initial thinking is that we should suppress creating
of Global Build Console in all the managers except the one dealing with
the default CDT console.

Could you create a bug and perhaps submit a patch as you seem to be the
interested party for that?


I have posted a proposed patch that fixes the problem.

Let me know if there any comments.  I would like to get this into Indigo.


-- Jeff J.


On Wed, Mar 23, 2011 at 3:52 PM, Jeff Johnston <jjohnstn@xxxxxxxxxx
<mailto:jjohnstn@xxxxxxxxxx>> wrote:

    With the latest EPP, I've noticed an issue with an Autotools project.

    The Autotools uses the CDT CBuildConsole extension to create a
    separate console for the configuration step output.

    The extension specifies an Autotools class which implements IConsole
    nearly identical to the CDT internal class CBuildConsole except we
    specify a console name and context id in the call to the console
    manager.  See code attached.

    The problem is that there are two CDT Global Build Consoles
    appearing. One that mirrors the contents of our configure console
    and one that mirrors the contents of the build console.  Both are
    named: CDT Global Build Console.

    The question is: what can be done to stop the repetition of the
    global console from occurring?

    -- Jeff J.

    cdt-dev mailing list
    cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>

cdt-dev mailing list

Back to the top