Eclipse could not resolve 'strcasecmp' [message #910557] |
Mon, 10 September 2012 01:31 |
Marjon Zubiri Messages: 5 Registered: September 2012 |
Junior Member |
|
|
I am trying to compile for a project for the STM32F103 processor.
I have CodeSourcery setup plus the STM32 CMSIS and Standard Peripheral libraries setup and ("supposedly") included in the Paths and Symbols of Eclipse (Juno).
I have a jumptable to sort of alias functions.
Other string.h related functions do not give any errors except for 'strcasecmp' which I use to alias 'strcmp'. Purpose being, I want calls to strcmp to not case about being case senstive.
If I do a build, and error shows.
And if I do an "F2" (focus) on the keyword 'strcasecmp' (which is where the error is), I get the error "'strcasecmp' undeclared here (not in a function)."
But if I highlight 'strcasecmp' and choose "Open Declaration", it shows where it is, which is in 'string.h' like the other string handling functions.
Code looks like below:
include <string.h>
const __attribute__((section(".jumptable"))) jmpTable JUMPT = {
.sprintf = &sprintf,
.strchr = &strchr,
.strlen = &strlen,
.strcat = &strcat,
.strcpy = &strcpy,
.strcmp = &strcasecmp,
.strncpy = &strncpy,
.strtol = &strtol,
.memcpy = &memcpy
};
Why is only strcasecmp affected? What am I doing wrong?
[Updated on: Mon, 10 September 2012 03:16] Report message to a moderator
|
|
|
Re: Eclipse could not resolve 'strcasecmp' [message #911013 is a reply to message #910557] |
Mon, 10 September 2012 20:08 |
Marjon Zubiri Messages: 5 Registered: September 2012 |
Junior Member |
|
|
219 views and no input? Please at least give some input. I have ran out of ideas and quite new to Eclipse and Linux. I was thinking it was the 'indexer' of Eclipse and have tried to check/uncheck different settings there but still nothing. When pressing F3 or Open Declaration, Eclipse is able to resolve that the declaration is in string.h
[Updated on: Mon, 10 September 2012 22:49] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03598 seconds