Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Include paths and Kepler (on Windows)
Include paths and Kepler (on Windows) [message #1227124] Fri, 03 January 2014 16:05
Juha Aaltonen is currently offline Juha AaltonenFriend
Messages: 3
Registered: January 2014
Location: Nokia, Finland
Junior Member
Any idea why the compiler often complains about definitions/declarations not found?

when going to the complaining location in the C file, selecting the complained-about thing and right-clikcing and selecting "find definition" finds it.
Also the path is in the include directory list.

Sometimes getting to the definition fixes the problem, sometimes not, and sometimes the definition is not found even if the file is in the include-path and definitions in the other files in that same path do not generate complaints.
Sometimes cleaning the project and building all removes the problem, sometimes not.

What could affect that? Eclipse-version? Using 64-bit Windows 7? gnu atm toolchain?
That has happened with 3 projects 2 of which have been downloaded "test projects".

[edit]
I forgot: also the the parameters for objdump, objcopy and size are "messed up".
Like the first parameter for objcopy is input file, flags, input file again and output file. The first input file and the flags seem to be in the same variable, but I'm not sure which. Is there a way to see what's in the variables? It's annoying having to remove the parameters from the command lines one at a time and then "build all" and wait for the console output and see what changed.

Are there some issues that could cause that in 64-bit windows 7 or maybe my installation is seriously corrupt?

[edit2]
The messed up parameters:
Command line options (from the project properties):
${COMMAND} ${INPUTS} ${FLAGS}
From console output:
arm-none-eabi-size "..\\USB_CDC_koe.elf" --format=berkeley USB_CDC_koe.elf

Command line options (from the project properties):
${COMMAND} ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX}${OUTPUT} ${INPUTS}
From console output:
arm-none-eabi-objdump USB_CDC_koe.elf --source --all-headers --demangle --line-numbers --wide > USB_CDC_koe.lst "..\\USB_CDC_koe.elf"

Command line options (added the '-v'):
${COMMAND} -v ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX}${OUTPUT} ${INPUTS}
From console output:
arm-none-eabi-objcopy -v USB_CDC_koe.elf -O ihex USB_CDC_koe.hex "..\\USB_CDC_koe.elf"

The path without ".." is the right one.

[edit3]
The command line parameters and console outputs are copied from 32-bit Vista installation, but the stuff is the same as with 64-bit Windows 7 installation.
So it doesn't seem to be a 32/64 bit issue, nor Windows 7 issue.

[Updated on: Sun, 05 January 2014 13:24]

Report message to a moderator

Previous Topic:HelloWorld.cpp fails on Juno/Mac
Next Topic:Kepler, Gnu ARM toolchain and OpenOCD
Goto Forum:
  


Current Time: Mon Nov 24 18:21:11 GMT 2014

Powered by FUDForum. Page generated in 0.02079 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software