Eclipse Community Forums: C / C++ IDE (CDT) » console scanner discovery not working

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » console scanner discovery not working

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

console scanner discovery not working [message #227032]

Wed, 19 November 2008 22:07

Keath Milligan

Messages: 38
Registered: July 2009

Member

I can't seem to get paths automatically added to my makefile projects
with Ganymede/CDT.

My makefile is outputting the gcc commands with a bunch of "-D" and "-I"
directives, but none of the paths are being added to the project.

When I go to project properties, I see that it does add the symbols, but
as built-ins. Paths are not added at all.

I also tried loading output from a file, but that doesn't work either.

--
Keath Milligan
Austin, Texas
http://keathmilligan.net

Report message to a moderator

Re: console scanner discovery not working [message #227063 is a reply to message #227032]

Thu, 20 November 2008 07:06

Ali Burak Kulakli

Messages: 116
Registered: July 2009

Senior Member

Is your console output prints current directory? For example

gnumake: Entering directory 'D:\workspace\project'

I did have some problems before because the build system we use did not
print this. After I enabled this (actually removed the parameter
"--no-print-directory"), this has started to work.

I hope this helps,
Burak

Keath Milligan wrote:
> I can't seem to get paths automatically added to my makefile projects
> with Ganymede/CDT.
>
> My makefile is outputting the gcc commands with a bunch of "-D" and "-I"
> directives, but none of the paths are being added to the project.
>
> When I go to project properties, I see that it does add the symbols, but
> as built-ins. Paths are not added at all.
>
> I also tried loading output from a file, but that doesn't work either.
>

Report message to a moderator

Re: console scanner discovery not working [message #227089 is a reply to message #227063]

Thu, 20 November 2008 14:21

Keath Milligan

Messages: 38
Registered: July 2009

Member

Hmm. I'll try this.

I did bring up CDT under the debugger and I was able to step into the
console parser. It is parsing out all of the directories and symbols,
but the directories never get added to the project.

Ali Burak Kulakli wrote:
> Is your console output prints current directory? For example
>
> gnumake: Entering directory 'D:\workspace\project'
>
> I did have some problems before because the build system we use did not
> print this. After I enabled this (actually removed the parameter
> "--no-print-directory"), this has started to work.

--
Keath Milligan
Austin, Texas
http://www.keathmilligan.net

Report message to a moderator

Re: console scanner discovery not working [message #227099 is a reply to message #227089]

Thu, 20 November 2008 20:49

Keath Milligan

Messages: 38
Registered: July 2009

Member

Ok, I tried having it output "Entering directory ..." statements and
this did not work either. I also had the makefile output directories in
varying forms of relative paths, full Windows-style paths and full
Cygwin-style paths, none get added to the project.

Keath Milligan wrote:
> Hmm. I'll try this.
>
> I did bring up CDT under the debugger and I was able to step into the
> console parser. It is parsing out all of the directories and symbols,
> but the directories never get added to the project.
>
> Ali Burak Kulakli wrote:
>> Is your console output prints current directory? For example
>>
>> gnumake: Entering directory 'D:\workspace\project'
>>
>> I did have some problems before because the build system we use did
>> not print this. After I enabled this (actually removed the parameter
>> "--no-print-directory"), this has started to work.

--
Keath Milligan
Austin, Texas
http://keathmilligan.net

Report message to a moderator

Re: console scanner discovery not working [message #227122 is a reply to message #227099]

Fri, 21 November 2008 02:12

Keath Milligan

Messages: 38
Registered: July 2009

Member

I figured out what was going on. Due to the weird way this project was
structured, the console parser was picking up the include paths, but
bailing before adding them to the project because it couldn't find the
source files that were being compiled.

--
Keath Milligan
Austin, Texas
http://keathmilligan.net

Report message to a moderator

Re: console scanner discovery not working [message #227141 is a reply to message #227122]

Fri, 21 November 2008 08:39

James Blackburn

Messages: 36
Registered: July 2009

Member

Keath Milligan wrote:
> I figured out what was going on. Due to the weird way this project was
> structured, the console parser was picking up the include paths, but
> bailing before adding them to the project because it couldn't find the
> source files that were being compiled.

If you get a chance to create a simple test project which exhibits the
problem, it would be great if you could attach that to bugzilla.
Ideally the scanner discovery should report problems such as this back
to the user...

Cheers,

James

Report message to a moderator

Previous Topic:	Too much MI commands send to gdb during debugging
Next Topic:	Newbie Q on libraries

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Sep 24 11:30:44 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter