CW 6.1 Access Paths

[kef]

I don't understand how CW for MCU's v6.1 finds library include files. In Access paths I see

{Compiler}ColdFire_Support\Libraries

{Compiler}ColdFire_Support\msl

{Compiler}ColdFire_Support\Runtime

{Compiler}ColdFire_Support\hcs08_compatibility

No path from listed above has any standard include files like stdio.h math.h etc. All include files are at least one level deeper than specified access path. I wonder how preprocessor finds required include files.

Say I include <math.h> in my code. What literature I should study to be able to find for example declaration of standard log() function. So many files, more than one declaration. It's absolutely not clear which one is right one.

Thanks

[CompilerGuru]

The second column, the one with a folder symbol, defines if all the subfolders should be searched as well.
Check the "Access Paths" topic in the manual, this preference panel is described.

To open a specific header like math.h, I usually use the Ctrl-D shortcut. Just enter the filename and CW opens it, it does consider the search path of the current project.

Daniel

[kef]

Thanks. Didn't know the meaning of that gray thing in second column :smileyhappy:. Manual explains that well, shame on me not looking at it before.

I was confused too by zilions of very smart defines in MSL headers. It was hard to find at first why I can't override some library functions. It was not easy to find where function is declared and with inline keyword etc. Some function have prototypes, then suddenly some macro define overrides that making preprocessing not able to tell the thruth.