CDT Build Console enhancements
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
CDT Build Console enhancements
by Dmitry Kozlov-2
::
Rate this Message:
Hello,
I'm working on some enhancements to CDT Build Console: - Run build button on concole toolbar, to run build directly from console - "Make arguments" text field on console toolbar to pass parameters to make when Run build is pressed - Build Console output text partitioning to enable moving between errors and going from errors to source code directly from console, not using problems view. - File prefixes translation in console preferences to enable view error in local source file while compiler reported error against remote filesystem, e.g. translate /net/user/project/src/ to C:\myProject\src. - Save console to file button on console toolbar. I suppose it is better to do it as existing console build modification instead of writing plugin with another console implementation. Can these modifications be included to CDT head? Who can help with review code and commiting this? Any other suggestions concerning this functionality from CDT team? Best regards, Dmitry Kozlov _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Christian W. Damus-3
::
Rate this Message:
Hi, Dimtry,
I'm not a CDT committer, but I do have an interest in this. Your enhancements strike me as very handy, especially the navigation between problems. That sounds excellent. For the make arguments, are they a one-shot deal (affecting only the next click of the in-console build button)? I assume that it is not intended to update the project configuration's make settings in the .cproject file ... that would be confusing. In my CDT extension I have a component that uses the C build console for projects that are concerned with C/C++ development but which do not build C/C++ source (neither using make nor otherwise). For such projects, it wouldn't make sense to show make arguments. Would I be able to suppress the make arguments input field for my projects? Could I program the Build button just run my project's installed builders, or will it be hard-wired to "make"? Also, about the save-to-file button: the console has a fixed buffer size (default 500 lines), so that for large/verbose builds, some output might be lost. That wouldn't be an issue if the save-to-file button actually selects a file *before* the build to which the build output would be "tee"d. That would be very cool. :-) Thanks for the initiative! Christian On Mon, 2009-10-19 at 19:23 +0400, Dmitry Kozlov wrote: Hello, I'm working on some enhancements to CDT Build Console: - Run build button on concole toolbar, to run build directly from console - "Make arguments" text field on console toolbar to pass parameters to make when Run build is pressed - Build Console output text partitioning to enable moving between errors and going from errors to source code directly from console, not using problems view. - File prefixes translation in console preferences to enable view error in local source file while compiler reported error against remote filesystem, e.g. translate /net/user/project/src/ to C:\myProject\src. - Save console to file button on console toolbar. I suppose it is better to do it as existing console build modification instead of writing plugin with another console implementation. Can these modifications be included to CDT head? Who can help with review code and commiting this? Any other suggestions concerning this functionality from CDT team? Best regards, Dmitry Kozlov _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by James Blackburn-2
::
Rate this Message:
Hi Dmitry,
2009/10/19 Dmitry Kozlov <ddk@...>: > I'm working on some enhancements to CDT Build Console: > - Run build button on concole toolbar, to run build directly from console How would this differ from the BuildAction in the toolbar or make targets in the make target view? > - "Make arguments" text field on console toolbar to pass parameters to > make when Run build is pressed > - Build Console output text partitioning to enable moving between errors > and going from errors to source code directly from console, not using > problems view. This sounds useful. > - File prefixes translation in console preferences to enable view error > in local source file while compiler reported error against remote > filesystem, e.g. translate /net/user/project/src/ to C:\myProject\src. This should be part of the ErrorParser framework, or there'll be a confusing disconnect between what the console is able to do and what the Problems view gives. There's also no point re-implementing the source resolution logic. I'm not sure how much of the above belongs in the Console. The builds have (so far) been run using the Eclipse project builder mechanism. Arguably, for Makefile projects, this is overkill as we don't care about resource deltas since last build and it's a pain having the Workspace locked. How would a console run build be different from the existing build mechanisms we've got? Cheers, James > - Save console to file button on console toolbar. > > I suppose it is better to do it as existing console build modification > instead of writing plugin with another console implementation. Can these > modifications be included to CDT head? Who can help with review code and > commiting this? > Any other suggestions concerning this functionality from CDT team? > > > Best regards, > Dmitry Kozlov > > > _______________________________________________ > cdt-dev mailing list > cdt-dev@... > https://dev.eclipse.org/mailman/listinfo/cdt-dev > cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Olexiy Buyanskyy
::
Rate this Message:
Do you have anything implemented?
I wish to participate. I think one enhancement can be useful. Dynamic processing of console output. Build can take several minutes and in many cases you want to see error and warning markers as soon they appear in console.
-- Olexiy 2009/10/19 Dmitry Kozlov <ddk@...> Hello, _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
RE: CDT Build Console enhancements
by Warren.Paul
::
Rate this Message:
It sounds like he just wants to add the same build toolbar to the console view which sounds fine. I don't like add command line arguments for make to the standard CDT build console since there are many other non-make based builders. That could potentially be added dynamically based on the type of project being built.
Hyperlinks of errors/warnings in the console view would be a great addition IMO. There's actually a bug (or two or three) about this with a good amount of history. I would recommend tracking that down so you can see whatever issues you might run into. I remember looking at doing that a year or two ago and ran into some problems that couldn't be solved without a decent refactor of the CDT build console. As James said, anything to do with parsing errors and resolving source locations should be done in the error parsing mechanism so the results are the same in both the console and problems view. Thanks, Warren >-----Original Message----- >From: cdt-dev-bounces@... >[mailto:cdt-dev-bounces@...] On Behalf Of ext James Blackburn >Sent: Monday, October 19, 2009 10:44 AM >To: CDT General developers list. >Subject: Re: [cdt-dev] CDT Build Console enhancements > >Hi Dmitry, > >2009/10/19 Dmitry Kozlov <ddk@...>: >> I'm working on some enhancements to CDT Build Console: >> - Run build button on concole toolbar, to run build directly from >> console > >How would this differ from the BuildAction in the toolbar or >make targets in the make target view? > >> - "Make arguments" text field on console toolbar to pass >parameters to >> make when Run build is pressed >> - Build Console output text partitioning to enable moving between >> errors and going from errors to source code directly from >console, not >> using problems view. > >This sounds useful. > >> - File prefixes translation in console preferences to enable view >> error in local source file while compiler reported error against >> remote filesystem, e.g. translate /net/user/project/src/ to >C:\myProject\src. > >This should be part of the ErrorParser framework, or there'll >be a confusing disconnect between what the console is able to >do and what the Problems view gives. There's also no point >re-implementing the source resolution logic. > >I'm not sure how much of the above belongs in the Console. The >builds have (so far) been run using the Eclipse project >builder mechanism. >Arguably, for Makefile projects, this is overkill as we don't >care about resource deltas since last build and it's a pain >having the Workspace locked. How would a console run build be >different from the existing build mechanisms we've got? > >Cheers, >James > >> - Save console to file button on console toolbar. >> >> I suppose it is better to do it as existing console build >modification >> instead of writing plugin with another console implementation. Can >> these modifications be included to CDT head? Who can help >with review >> code and commiting this? >> Any other suggestions concerning this functionality from CDT team? >> >> >> Best regards, >> Dmitry Kozlov >> >> >> _______________________________________________ >> cdt-dev mailing list >> cdt-dev@... >> https://dev.eclipse.org/mailman/listinfo/cdt-dev >> >_______________________________________________ >cdt-dev mailing list >cdt-dev@... >https://dev.eclipse.org/mailman/listinfo/cdt-dev >_______________________________________________ cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Andrew Gvozdev-2
::
Rate this Message:
Hi Dmitry,
I am pretty much with James on that:
- Run build button on concole toolbar, to run build directly from console These sound like a duplication of toolbar build button and/or Make Targets View functionality. I am not against the idea but for reusing those elements when appropriate.
- Build Console output text partitioning to enable moving between errors This would be great to have. There have been a few attempts to do so far like bug 50124 but did not come to fruition.
- File prefixes translation in console preferences to enable view error I agree with James, this should be part of ErrorParsers framework or maybe even a part of a toolchain where there is a special provider for converting those like cygwin paths. Ideally it should be generalized to support error parsers as well.
- Save console to file button on console toolbar. This would be useful. Maybe a button to re-parse saved output by error parsers could be useful too. I suppose it is better to do it as existing console build modification I suggest to open a bug (or use one of those existing) and if you have a patch attach it there. We'll take a look.
Thanks, Andrew
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
subdir.mk rule for XL UPC wrong?
by Nenad Vukicevic
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
and CDT 6.0.1 and tried to create a toolchain for GCCUPC (gccupc.org) compiler. I was able to model it based on XL UPC, however, I am not able to compile any code because of the wrong subdir.mk file. I was able to duplicate the problem with XL UPC compiler too. This is a rule I get for UPC files (my example has two upc files): #
Each
subdirectory must supply rules for building sources it contributes I don't know how xlupc behaves, but our gcc based compiler complains with multiple source files specified with "-c" switch. I this an error or I am doing something wrong. I only created a project as executable XL UPC, created two source files, and created a build configuration with Make Targets->Build. Nenad _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Andrew Gvozdev-2
::
Rate this Message:
On Mon, Oct 19, 2009 at 12:00 PM, <Warren.Paul@...> wrote:
Hyperlinks of errors/warnings in the console view would be a great addition IMO. There's actually a bug (or two or three) about this with a good amount of history. I would recommend tracking that down so you can see whatever issues you might run into. I remember looking at doing that a year or two ago and ran into some problems that couldn't be solved without a decent refactor of the CDT build console. It must be bug 203727 you are talking about Andrew _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
RE: CDT Build Console enhancements
by Warren.Paul
::
Rate this Message:
That's the one.
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: subdir.mk rule for XL UPC wrong?
by Chris Recoskie
::
Rate this Message:
Something is definitely going wrong in the makefile generation... it should not be doing that. It might be a bug in the generator or a bug in the toolchain. I'm guessing the latter because no one has been complaining about this for GCC projects. Can you please file a bug? Thanks.
I am new to eclipse and it might be that I am doing something wrong. I installed the latest eclipse and CDT 6.0.1 and tried to create a toolchain for GCCUPC (gccupc.org) compiler. I was able to model it based on XL UPC, however, I am not able to compile any code because of the wrong subdir.mk file. I was able to duplicate the problem with XL UPC compiler too. This is a rule I get for UPC files (my example has two upc files): # Each subdirectory must supply rules for building sources it contributes %.o: ../%.upc @echo 'Building file: $<' @echo 'Invoking: XL UPC Compiler' /opt/ibmcmp/xlupc -c -O0 -g -o"$@" "$<" "../test.upc" "../test1.upc" @echo 'Finished building: $<' @echo ' '
|
|||||||||||
|
|
Can't act with mouse on some buttons
by starbright
::
Rate this Message:
Just tested the Eclipse on Mandriva Linux.
Seems to work with one exception: I can't cause an action with some buttons by mouse. As example: NEW / C-Project / name ... : I can't act Next or Finish by mouse, but I can do Cancel by mouse. To do "next" I have to move mouse on the button (it will be colored then) and press Enter on keyboard. What can be the reason for that? Tested this with 2 different Eclipse version, so something seems to be missing in system. Compiling .. works fine. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Dmitry Kozlov-2
::
Rate this Message:
Thank you guys for your interest and for many useful ideas. I want to
sum up all questions and comments and provide some answers. 1. Run build button from console. I just trying to reuse existing build mechanism as it is used in TargetBuild class. 2. I will make preference in build console whether to show make arguments text field. If you can tell me for what kind of projects it should be enabled/disabled please advice and I will make this determined automatically. These make args provided by user are not used to update project configuration but work as one-shot deal just for make which is run pressing Run Build button at console toolbar. 3. Saving console now is implemented as saving current console content but not full build output. It is very good idea to use tee. I will take a look at this. Olexiy, you can help with this if you want. 4. I want to reuse error parsers to partition console output, but this is not implemented yet. I'm familiar with 50124 implementation and I will look at 203727, many thanks for this information. I'm not intended to use my own error parsing as it is done in 50124. It is the general answers, but there are some technical problems which I want to discuss separately: 1. There a problem with TargetBuild: it is from cdt.make.ui, but console is in cdt.ui so using this results cyclic dependency between cdt.make.ui and cdt.ui because cdt.make.ui already depends on cdt.ui. In my current prototype implementation I copypasted TargetBuild to cdt.ui and slightly modified it. Are there other ideas how to cope with this without copy-past? 2. To partition console output according errors I expected to reuse markers at Problems view, created by existing error parsers, but I failed to find public API to markers and this code unfortunately is part of platform, not the CDT. So there are 2 questions: 1) any idea how to do this without platform modification, 2) is it easy to check in appropriate platform modification motivated by needs of CDT project, can somebody help with lobbying this? Dmitry _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
RE: CDT Build Console enhancements
by Brunauer, Walter
::
Rate this Message:
ad technical problem 2.:
org.eclipse.core.resources.IResource.createMarker(String type) and org.eclipse.core.resources.IResource.findMarkers(String type, boolean includeSubtypes, int depth) should provide all you need. HTH, Walter > -----Original Message----- > From: cdt-dev-bounces@... > [mailto:cdt-dev-bounces@...] On Behalf Of Dmitry Kozlov > Sent: Dienstag, 20. Oktober 2009 13:02 > To: CDT General developers list. > Cc: Nathan Sidwell > Subject: Re: [cdt-dev] CDT Build Console enhancements > > Thank you guys for your interest and for many useful ideas. I > want to sum up all questions and comments and provide some answers. > > 1. Run build button from console. I just trying to reuse > existing build mechanism as it is used in TargetBuild class. > 2. I will make preference in build console whether to show > make arguments text field. If you can tell me for what kind > of projects it should be enabled/disabled please advice and I > will make this determined automatically. > These make args provided by user are not used to update > project configuration but work as one-shot deal just for make > which is run pressing Run Build button at console toolbar. > 3. Saving console now is implemented as saving current > console content but not full build output. It is very good > idea to use tee. I will take a look at this. Olexiy, you can > help with this if you want. > 4. I want to reuse error parsers to partition console output, > but this is not implemented yet. I'm familiar with 50124 > implementation and I will look at 203727, many thanks for > this information. I'm not intended to use my own error > parsing as it is done in 50124. > > > It is the general answers, but there are some technical > problems which I want to discuss separately: > > 1. There a problem with TargetBuild: it is from cdt.make.ui, > but console is in cdt.ui so using this results cyclic > dependency between cdt.make.ui and cdt.ui because cdt.make.ui > already depends on cdt.ui. In my current prototype > implementation I copypasted TargetBuild to cdt.ui and > slightly modified it. Are there other ideas how to cope > with this without copy-past? > > 2. To partition console output according errors I expected to > reuse markers at Problems view, created by existing error > parsers, but I failed to find public API to markers and this > code unfortunately is part of platform, not the CDT. So there > are 2 questions: 1) any idea how to do this without platform > modification, 2) is it easy to check in appropriate platform > modification motivated by needs of CDT project, can somebody > help with lobbying this? > > > Dmitry > _______________________________________________ > cdt-dev mailing list > cdt-dev@... > https://dev.eclipse.org/mailman/listinfo/cdt-dev > cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Andrew Gvozdev-2
::
Rate this Message:
Hi Dmitry,
On Tue, Oct 20, 2009 at 7:01 AM, Dmitry Kozlov <ddk@...> wrote: Thank you guys for your interest and for many useful ideas. I want to sum up all questions and comments and provide some answers. If you want to do builds from the console perhaps combobox listing existing make targets would be appropriate?
2. I will make preference in build console whether to show make arguments text field. If you can tell me for what kind of projects it should be enabled/disabled please advice and I will make this determined automatically. It should not be only make arguments but user rather should be able to specify the whole command. Then, sometimes there is a need to run several commands at one shot. Inability to do so is pretty annoying in Make Targets View.
The feature should be enabled for all projects. These make args provided by user are not used to update project configuration but work as one-shot deal just for make which is run pressing Run Build button at console toolbar. Do you intend to persist the entered command to be able to rerun later?
3. Saving console now is implemented as saving current console content but not full build output. It is very good idea to use tee. I will take a look at this. Olexiy, you can help with this if you want. It is probably better to specify where to save outputs before the build started, not afterwards. It would also avoid the problem of not full output. 4. I want to reuse error parsers to partition console output, but this is not implemented yet. I'm familiar with 50124 implementation and I will look at 203727, many thanks for this information. I'm not intended to use my own error parsing as it is done in 50124. Copy-paste does not sound like a reasonable solution to me. There must be a better way. 2. To partition console output according errors I expected to reuse markers at Problems view, created by existing error parsers, but I failed to find public API to markers and this code unfortunately is part of platform, not the CDT. So there are 2 questions: 1) any idea how to do this without platform modification, 2) is it easy to check in appropriate platform modification motivated by needs of CDT project, can somebody help with lobbying this? ErrorParserManager keeps the list of errors (markers) collected during a build. It is private but we could add a getter for the greater good. It is not hard to add build output line number in the marker properties too.
A couple more ideas: - Currently builds lock the whole workspace. Perhaps it is reasonable to have an option to run such console command without locking and refresh? There are many workflows which would benefit like remote compilation. This would also help with a problem with markers appearing only after build is finished mentioned by Olexiy.
- Console View could have an options menu which many other views sport - the little triangle at top-right corner of a view. It open console preferences or other options. Andrew
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by James Blackburn-2
::
Rate this Message:
2009/10/20 Andrew Gvozdev <angvoz.dev@...>:
> - Currently builds lock the whole workspace. Perhaps it is reasonable to > have an option to run such console command without locking and refresh? > There are many workflows which would benefit like remote compilation. This > would also help with a problem with markers appearing only after build is > finished mentioned by Olexiy. I'm going to be looking at this at some point over the next couple months. I've had some success with using more relaxed scheduling rules for makefile builds. This requires some platform support (which now exists) although deltas since last build is broken, I believe. Given that all CDT builds are run form the Eclipse builder, this issue is somewhat orthogonal to Console improvements, and I think should remain separate. Cheers, James > - Console View could have an options menu which many other views sport - the > little triangle at top-right corner of a view. It open console preferences > or other options. > Andrew >> >> >> Dmitry >> _______________________________________________ >> cdt-dev mailing list >> cdt-dev@... >> https://dev.eclipse.org/mailman/listinfo/cdt-dev > > > _______________________________________________ > cdt-dev mailing list > cdt-dev@... > https://dev.eclipse.org/mailman/listinfo/cdt-dev > > cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Christian W. Damus-3
::
Rate this Message:
Hi, Dmitry, Andrew,
On the question of which projects should have the make arguments and/or command-line input available: the build console is not currently restricted to projects that use make. Indeed, it isn't even restricted to projects that have the C nature. In such applications it doesn't always make sense to present the make override options. Perhaps the make arguments UI can be shown only for projects that have the CDT Common Builder installed and/or C Nature? I don't want to give my users the impression that a project is built with "make" or some other external tool when it isn't. Having the Build button in such cases simply run the default builder for the project is still pretty cool, of course. :-) Cheers, Christian On Tue, 2009-10-20 at 09:35 -0400, Andrew Gvozdev wrote: --------8<-------- 2. I will make preference in build console whether to show make arguments text field. If you can tell me for what kind of projects it should be enabled/disabled please advice and I will make this determined automatically. It should not be only make arguments but user rather should be able to specify the whole command. Then, sometimes there is a need to run several commands at one shot. Inability to do so is pretty annoying in Make Targets View. The feature should be enabled for all projects. -------->8--------
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Andrew Gvozdev-2
::
Rate this Message:
Hi Christian,
I think it would be pretty cool to be able to run an arbitrary command on any project parsing output with customized error parser and get error markers appear in files referred in output. Why should it be C Nature only? There are plenty of tools not necessarily compilers and they could be run on different kind of files. In the Console View I really see this as "Run" and not "Build" command.
Andrew
On Tue, Oct 20, 2009 at 9:56 AM, Christian W. Damus <cdamus@...> wrote:
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Christian W. Damus-3
::
Rate this Message:
Hi, Andrew,
Yes, that is quite another matter, then! I agree. As it happens, my projects are built using an external tool, just not anything like make. It would be nice to be able to pre-populate this UI with the default command-line for my build tool! In any case, perhaps letting the UI not be overtly make-centric (e.g., no "Make command:" label but rather "Run command:") addresses my concern and retains the undeniable utility of the ad hoc "run command" capability. cW On Tue, 2009-10-20 at 10:16 -0400, Andrew Gvozdev wrote: Hi Christian, I think it would be pretty cool to be able to run an arbitrary command on any project parsing output with customized error parser and get error markers appear in files referred in output. Why should it be C Nature only? There are plenty of tools not necessarily compilers and they could be run on different kind of files. In the Console View I really see this as "Run" and not "Build" command. Andrew On Tue, Oct 20, 2009 at 9:56 AM, Christian W. Damus <cdamus@...> wrote: Hi, Dmitry, Andrew, 2. I will make preference in build console whether to show make arguments text field. If you can tell me for what kind of projects it should be enabled/disabled please advice and I will make this determined automatically. -------->8--------
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: CDT Build Console enhancements
by Doug Schaefer-4
::
Rate this Message:
Definitely, we've had numerous requests for SCons, CMake, Jam support. So we have to be sensitive to that.
Also, how does scanner discovery fit into this picture? It runs as a separate builder. Would running this command without Eclipse builder support break that? :D On Tue, Oct 20, 2009 at 10:23 AM, Christian W. Damus <cdamus@...> wrote:
_______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
|||||||||||
|
|
Re: Can't act with mouse on some buttons
by Olexiy Buyanskyy
::
Rate this Message:
What version of KDE do you use?
-- Olexiy
On Tue, Oct 20, 2009 at 3:28 AM, <star@...> wrote: Just tested the Eclipse on Mandriva Linux. _______________________________________________ cdt-dev mailing list cdt-dev@... https://dev.eclipse.org/mailman/listinfo/cdt-dev |
Nenad Vukicevic <
pic25965.gif (1K) | < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
