Eclipse Community Forums: C / C++ IDE (CDT) » Use Build Output Parser (BOP) to find include path

Home » Language IDEs » C / C++ IDE (CDT) » Use Build Output Parser (BOP) to find include path(What are the settings needed for this to work?)

Show: Today's Messages :: Show Polls :: Message Navigator

Use Build Output Parser (BOP) to find include path [message #1082383]

Thu, 08 August 2013 13:53

Martin Stolpe

Messages: 2
Registered: August 2013

Junior Member

Hello,

I'm trying to setup CDT so that I can work on a little kernel driver tutorial I've found.

CDT offers the "Build Output Parser (BOP)" options which is supposed to extract the include paths from the build output.

What options do I have to set for this to work with gnu make and gcc? Unfortunately I haven't found anything on the internet about this topic.

I'm currently using CDT 8.2.0.

Regards
Martin

[Updated on: Thu, 08 August 2013 15:45]

Report message to a moderator

Re: Use Build Output Parser (BOP) to find include path [message #1082495 is a reply to message #1082383]

Thu, 08 August 2013 16:46

Andrew Gvozdev

Messages: 257
Registered: July 2009

Senior Member

Try http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fconcepts%2Fcdt_c_scanner_discovery.htm

Andrew

Report message to a moderator

Re: Use Build Output Parser (BOP) to find include path [message #1082901 is a reply to message #1082495]

Fri, 09 August 2013 07:15

Martin Stolpe

Messages: 2
Registered: August 2013

Junior Member

Hi,

unfortunately I don't see any hints on how to configure CDT and the make and GCC command line parameters. I have uploaded the current project and build output with a screenshot of my current Build Output Parser settings.

Attachment: kernel_device_driver.zip
(Size: 20.72KB, Downloaded 162 times)
Attachment: build_output.txt
(Size: 5.85KB, Downloaded 455 times)
Attachment: preprocessor_include_paths_providers.png
(Size: 102.68KB, Downloaded 356 times)

Report message to a moderator

Re: Use Build Output Parser (BOP) to find include path [message #1083107 is a reply to message #1082901]

Fri, 09 August 2013 13:35

Andrew Gvozdev

Messages: 257
Registered: July 2009

Senior Member

It considers lines that start with "gcc" and end with C file being compiled. Your compile command is embedded into shell script. If you manage to print the compile command in build output on separate line it should parse it. Also, the C file has to be a part of the project.

Thanks,
Andrew

Report message to a moderator

Previous Topic:	Add default run-configuration on project create
Next Topic:	ASTRewrite and Preprocessor Macros

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 19:53:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter