Then pull the current source code and start there. git clone git://github.com/tinyprod/nesc.git
On Wed, Nov 7, 2012 at 2:42 AM, Enrico Scopelliti <[email protected]>wrote: > Yes, but I would like to understand the translation process that leads > to this app.c file. > > Thanks for the answer. > > Il 07/11/2012 02:52, Eric Decker ha scritto: > > if you just do a normal tinyos compilation you will get a > build/<platform>/app.c output file. > > That is the translated C file from nesc. > > > On Tue, Nov 6, 2012 at 5:32 AM, Enrico Scopelliti <[email protected]>wrote: > >> Hi to all, >> >> thanks for accepting me in TinyOS mailing list. >> >> I need some help about the compilation process in TinyOS. >> I have understood, thanks to "nesc-internal" page in TinyOS-Wiki, that >> there is a perl script (nesc-compile) that "invokes nesc1 to transform >> nesC application into a C file,and then invokes gcc to compile this C >> file". >> Can I use nesc1 options to give me a C file (possibly not pre-processed) >> in output? >> I'm interested to understand how nesc1 manipulates the ".nc" files to >> transform them in C files, so I would like to understand how I can use >> nesc compilator options (in general) to view all the transformations >> made to ".nc" application files to have an unique C file. >> >> Excuse for my English, I hope that you understand my question/problem. >> >> Any help is appreciated. >> >> Thanks to all. >> >> Have a nice day. >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
