Re: [cdt-dev] Build console location

[Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>]

Does anyone object having console in own plugin?

On Fri, Jul 23, 2010 at 12:08 PM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx> wrote:
> On Fri, Jul 23, 2010 at 11:00 AM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
>>
>> Actually, what I'm seeing is black text on a black background. I can
>> highlight the text in the console and see that it's there.
>>
>> Often, it's just creating a test project. I'll try to remember which
>> one it was, either Executable or Makefile, the next time I see it. But
>> that shouldn't really matter since the coloring should be independent
>> from the choice of builder.
>
> It more depends on *how* you used to build your projects than on project
> type. Do you use context menu, main menu, build icon, Ctrl-B or something
> else? We got a multitude of ways to build.
>
> Actually, the black console problem is very relevant to build console
> location we are discussing. The location of the console in cdt.ui is one of
> several factors resulting in black console bug (the root cause being bug
> 214215 Synchronization issue the first time preferences are accessed.) The
> problem is that when you do a build, build plugin spawns another thread
> which starts the console. The console located in cdt.ui plugin and inits
> cdt.ui preference store. In the meantime, the first thread keeps going and
> may/does also access some other facility in cdt.ui initializing the
> preference store. So there is a race condition where we hit bug 214215. I
> don't really see a good way to get around it currently. Should console be
> located in build plugin or its own plugin we wouldn't have that embarrassing
> issue.
>
> Andrew
>
>>
>> On Thu, Jul 22, 2010 at 11:21 PM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx>
>> wrote:
>> > Which builder is being run in your case? Is it CommonBuilder,
>> > MakeBuilder or
>> > some custom builder? How do you build your project?
>> >
>> > Andrew
>> >
>> > On Thu, Jul 22, 2010 at 10:49 PM, Doug Schaefer <cdtdoug@xxxxxxxxx>
>> > wrote:
>> >>
>> >> I get it quite often too. Haven't been able to figure a pattern to it.
>> >>
>> >> On Thu, Jul 22, 2010 at 6:29 PM, Marc Khouzam
>> >> <marc.khouzam@xxxxxxxxxxxx>
>> >> wrote:
>> >> > Speaking of build console, I see the black build console more often
>> >> > these days.
>> >> > I have it right now and I can't get rid of it without restarting.
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: cdt-dev-bounces@xxxxxxxxxxx
>> >> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alena Laskavaia
>> >> >> Sent: Thursday, July 22, 2010 1:13 PM
>> >> >> To: CDT General developers list.
>> >> >> Subject: Re: [cdt-dev] Build console location
>> >> >>
>> >> >> How about we move console to its own plugin? Would it help?
>> >> >> It would be breakage but we can have 8.0 not 7.1.
>> >> >>
>> >> >> On Wed, Jul 21, 2010 at 11:52 AM, Doug Schaefer
>> >> >> <cdtdoug@xxxxxxxxx> wrote:
>> >> >> > The idea is that the build console is independent of whatever
>> >> >> > build
>> >> >> > system you are using. I disagree that it should be moved.
>> >> >> >
>> >> >> > On Wed, Jul 21, 2010 at 11:43 AM, Andrew Gvozdev
>> >> >> <angvoz.dev@xxxxxxxxx> wrote:
>> >> >> >> Hi,
>> >> >> >> There is an enhancement request bug 297222 Allow temporary
>> >> >> build arguments
>> >> >> >> from build console  and there is an interest in that from
>> >> >> the community and
>> >> >> >> a submitted patch. However, this change is not possible
>> >> >> with the current
>> >> >> >> location of build console in cdt.ui.
>> >> >> >>
>> >> >> >> I created bug 320521 Move build console from cdt.ui to one
>> >> >> of the build
>> >> >> >> plugins to resolve this issue:
>> >> >> >>
>> >> >> >> The location of the build console in cdt.ui prevents
>> >> >> better integration of
>> >> >> >> the console with other build components. This task is a
>> >> >> blocker for bug
>> >> >> >> 297222, and I've run into it before on a few occasions too.
>> >> >> >> Currently the console classes are located in internal
>> >> >> packages of cdt.ui.
>> >> >> >> The suggested location is org.eclipse.cdt.make.ui so it
>> >> >> would be accessible
>> >> >> >> in other build plugins.
>> >> >> >>
>> >> >> >> Please, voice any concerns related to the issue.
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Andrew
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> cdt-dev mailing list
>> >> >> >> cdt-dev@xxxxxxxxxxx
>> >> >> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >> >> >>
>> >> >> >>
>> >> >> > _______________________________________________
>> >> >> > cdt-dev mailing list
>> >> >> > cdt-dev@xxxxxxxxxxx
>> >> >> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >> >> >
>> >> >> _______________________________________________
>> >> >> cdt-dev mailing list
>> >> >> cdt-dev@xxxxxxxxxxx
>> >> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >> >> _______________________________________________
>> >> > cdt-dev mailing list
>> >> > cdt-dev@xxxxxxxxxxx
>> >> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >> >
>> >> _______________________________________________
>> >> cdt-dev mailing list
>> >> cdt-dev@xxxxxxxxxxx
>> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >
>> >
>> > _______________________________________________
>> > cdt-dev mailing list
>> > cdt-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> >
>> >
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>