On Mon, Jul 6, 2009 at 8:56 PM, trilok i <[email protected]> wrote:
> hi all, > > My doubt is, how nesC compiler takes arguments from Makefile. > The way this works is make runs and uses the the tinyos build system which tells make what to include. Make runs nesc and feeds the application nc file to the compiler. The compiler figures out what to include by following the wiring. The easiest thing to do is to do stuff with the wiring via the application and at the place where the security module needs to get wired in. This can be turned on and off by the use of a define which would be turned on in the application makefile. I don't know how you need to wire your code in. But the wiring changes and code changes can be surrounded by something like: #ifdef USE_MY_SEC_MODULE changes.. #endif Then in the application makefile you would put something like: PFLAGS += USE_MY_SEC_MODULE Also see: TinyOS_Toolchain<http://docs.tinyos.net/index.php/TinyOS_Toolchain> eric Suppose i want to design a security algorithm, in such a case, how can I > enable and disable my algorithm from Makefile just like minisec and TinySec. > How can I make My algorithm known to nesC compiler? i.e if I set Macro to > True in Makefile my algorithm has to be enable. Is there any Way? > ------------------------------ > Videos Get the latest video streams on movies, Try > it!<http://video.msn.com/?mkt=en-in> > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- Eric B. Decker Senior (over 50 :-) Researcher Autonomous Systems Lab Jack Baskin School of Engineering UCSC
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
