[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] CDT Build Console enhancements
|
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@xxxxxxx> wrote:
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@xxxxxxx> wrote:
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@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
