On Dec 17, 2007 11:49 PM, David Gay <[EMAIL PROTECTED]> wrote: > On Dec 17, 2007 2:16 PM, John Griessen <[EMAIL PROTECTED]> wrote: > > What makes the .platform file necessary separately from the > ecosens1.target > > file? Could the ecosens1.target do it all somehow? > > The .platform file is for ncc (and mig and ncg). The .target file is > something used by the Makefile-based build system for TinyOS, and > contains things unrelated to what ncc needs/wants (e.g. information on > how to reprogram motes). Ideally at least there should be no > duplication between the information in a .target and .platform file... > > Merging the two files is, to me at least, a bad idea: > - If all the .platform stuff moves into .target: you can't build > anything without using the "magic" build system. This would be like if > gcc wasn't usable without some magic very large Makefile. > - If all the .target stuff moved into .platform: this would hardwire > specific programmers, preferred compilation flags, etc into ncc. > > Another reason why the merging would be a bad idea is the loss of the .family / .platform hierarchy. The .family file can be used to separate between the component set implementing the generic platform family features and the ones for the specific platforms. At the moment, it looks like the eyesIFX is the only place in the tree where this is used, but for me it provides a nice hierarchical model of the platform organization at the ncc level of abstraction.
Vlado
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
