On 5/19/06, Michael Schippling <[EMAIL PROTECTED]> wrote:
As for the include path, I meant the implicit path. For instance nothing explicitly references hardware.h (in most apps anyway),
hardware.h is referenced from tos.h, which is "magically" included when you compile a TinyOS program (but if you pass -v to ncc, you will see somewhere a -fnesc-include=tos option, which is the source of the magic...)
but it automagically appears in the (pre-)compiled code, and, various source directories are searched in some (unspecified to me) order when compiling.
Well, as I said, make sure ncc gets a -v option, and you will see the full set of include paths searched.
oh, and my (hopefully vanilla and regular-guy kinda) TOS 1.1.7 install doesn't find a man page for ncc...is it really part of the standard install, and I didn't set my MANPATH right?
I did say "the latest toolchain" ;-) The TinyOS 2.x toolchain is supposed to work with TinyOS 1.x as of TinyOS 1.1.<something recent>. But looking at the release date for 1.1.15, I guess my fixes for using the 2.x toolchain in 1.x haven't made it out of CVS and into a minor release :-( David Gay _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
