Show Posts
1
NXPTM M522XX, KINETIS and i.MX RT / KDS Highlighting issues
« on: March 19, 2015, 12:28:24 AM »
Hello, I was wondering if anyone has successfully got the highlighting of preprocessor blocks to work correctly in KDS.
I did have to disable eclipse's "Scalability" settings for it to work on larger files like kinetis.c
It is sort of working now, but there are still a few crucial symbols it refuses to recognize.
First are the predefined symbols (I see these in my configuration properties -> C/C++ General -> Paths and Symbols -> Symbol tab)
_GNU
_KDS
_KINETIS
These are sent to the compiler with option "-D_GNU" etc during a build, but eclipse editor seems to ignore them. Not sure if there is a setting in KDS to make it code highlight these approprialtely?
The other big one I noticed is OPSYS_CONFIG, which is defined in kinetis.c
KDS thinks this is not defined when viewing TaskConfig.h or config.h which each have #ifdef blocks for it.
This means when I try to search C/C++ fies it basically ignores my entire TaskConfig.h, which is incredibly annoying.
I did have to disable eclipse's "Scalability" settings for it to work on larger files like kinetis.c
It is sort of working now, but there are still a few crucial symbols it refuses to recognize.
First are the predefined symbols (I see these in my configuration properties -> C/C++ General -> Paths and Symbols -> Symbol tab)
_GNU
_KDS
_KINETIS
These are sent to the compiler with option "-D_GNU" etc during a build, but eclipse editor seems to ignore them. Not sure if there is a setting in KDS to make it code highlight these approprialtely?
The other big one I noticed is OPSYS_CONFIG, which is defined in kinetis.c
KDS thinks this is not defined when viewing TaskConfig.h or config.h which each have #ifdef blocks for it.
This means when I try to search C/C++ fies it basically ignores my entire TaskConfig.h, which is incredibly annoying.