Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320823 - Provide a way to use existing error parsers for external tools
Summary: Provide a way to use existing error parsers for external tools
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 7.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-24 16:31 EDT by Dmitry Nezhevenko CLA
Modified: 2020-09-04 15:19 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Nezhevenko CLA 2010-07-24 16:31:44 EDT
Build Identifier: CDT 7.0

It will be useful if eclipse will allow to specify error parsers for External tool configurations. 

For example one of configured by me external tools calls for compiler for one of source files. And it will be very cool to get it's output parsed so that errors are displayed in "problems" view.

Reproducible: Always
Comment 1 Andrew Gvozdev CLA 2010-07-24 23:03:07 EDT
It is normally done in Make Targets View. Create a new "Target", uncheck "Use build settings" and enter build command. Then you can run your command with a double-click and get your problem markers.

External Tools Configurations would possible go along with bug 295626.
Comment 2 Dmitry Nezhevenko CLA 2010-07-25 04:28:22 EDT
Hi,

Thanks, this is partially useful. But as far as I know, it's impossible to pass some custom variables to make target (like current opened file name, etc).

But for tools that have no any "input" parameters that sounds good.
Comment 3 Axel Mueller CLA 2010-08-25 02:23:15 EDT
(In reply to comment #2)
> Hi,
> 
> Thanks, this is partially useful. But as far as I know, it's impossible to pass
> some custom variables to make target (like current opened file name, etc).
> 
> But for tools that have no any "input" parameters that sounds good.
You can use Eclipse variables in Make Targets. E.g.
${selected_resource_path}
/project_in_workspace/src/test.cpp
${selected_resource_name}
test.cpp
${selected_resource_loc}
/home/user/path_to_workspace/project/src/test.cpp
Comment 4 Andrew Gvozdev CLA 2010-11-16 09:46:03 EST
But be aware that those variables work unreliably and can cause deadlocks. See also bug 260524.