ah ha, is that le différance between "#include" and "includes"?
Which process does inclusion/expansion.
If so, is there a dependency issue?
thx
MS
David Gay wrote:
On 5/21/06, Michael Schippling <[EMAIL PROTECTED]> wrote:
Just got around to trying the ncc -v thing and funnily enough
it doesn't list "hardware.h" in it's pre-processing step. It
does mention tos.h, so perhaps nested includes are not detailed?
Preprocessing is handled by the C preprocessor, so -v won't show
anything about #include directives (basically you'll see components,
and files loaded with "includes").
Note that you can also find out where a file is located by looking in
the generated C file (usually build/<platform>/app.c) - it's full of #
"<filename>" <linenumber> directives. The <filename> is either an
absolute or app-directory-relative path.
David Gay
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
