> > I do. Why should contrib -- a social construction that happens to be > the way it is mostly due to sourceforge licensing and CVS checkout > structure -- determine parameters to the compiler? If contrib were in > tinyos-2.x (as it is in 1.x), then this would not be necessary.
Why even have the %T then? You can always use $TOSDIR or explicitly write out the path each time you want to reference it. Its there purely for convenience (its not in fact a 'parameter' to the compiler in the sense of a command line parameter. Look at how ncc deals with the %T... it just looks up what TOSDIR is and replaces it). > It might make more sense to define a variable in Makerules that > derives contrib from TOSDIR/TOSROOT. Application makefiles can > override it, etc. While I agree it might be a social construct that contrib is in a separate tree in T2, that doesn't mean we can ignore this fact. When someone checks out contrib from sourceforge they have the freedom to place it anywhere in their directory heirarchy that they like. The only way we could have makerules 'derive' contrib from TOSROOT is if we force users to place their contrib directory at some location underneath the tinyos-2.x tree heirarchy. I personally, like to leave it outside...... To deal with this, I simply set a new environment variable that points to my TOSCONTRIBROOT and reference everything from there. Adding the %C to ncc would just allow %C to stand in place of $TOSCONTRIBROOT just like %T stands in place of $TOSDIR. I personally don't see anything wrong with doing this..... Kevin
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
