On Wed, Aug 17, 2011 at 4:41 PM, Thomas Kothmayr <[email protected]> wrote:
> Hello, > > due to various legal constraints I am required to provide certain > modules of my nesC program to other contributors only in binary form. Is > there a simple way to compile specific nesC modules to a .o file or > something similar? > Not to my knowledge. NesC is intended to involve whole program compilation which is anthetical to what you are trying to do. Given that nesc invokes the underlying toolchain and you can see this by specifing verbose on the command line, you can probably figure out a way to mess with it. You could also tell nesc to just output the resultant C application file (the intermediate C code) and try to do something with that. But I don't think it would be easy to interface to it because by intention all of the routines are declared static in the intermediary C code so aren't exported to the linker. Otherwise, my idea would be to port these portions of the code to C and > then link them in as binaries. The target is one specific mote > architecture. Would there be anything specific that I have to take care > of when compiling? > Hard to answer that question because the development context you are describing is so far outside the typical tinyos development context. > Thank you for your help. > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
