[Tinyos-help] .platform question

[Michael Schippling]

Along these lines...is there a doc that describes the structure of
the TOS devel trees and their position dependencies? I've discovered
by wanton experimentation that I can set TOSDIR/TOSROOT (but, hmm,
which one, and using which (cygwin-hack C:/opt) syntax?) in order to
use different T1 version trees -- but strangely, boomerang has a
little finger reaching into "tinyos-1.x" to get Makerules -- and
I surely would like to put my own personal apps in my own personal
dev tree (just so I can keep them together with their host programs
and backup everything at once), say pointed to by "contrib" or something.
But I haven't been brave enough to try compiling TOS apps outside the
/opt/tinyos* umbrella because I just know there's going to be a
"../../.." in a Makefile someplace.

This is not entirely wishful thinking because of a quirk in Eclipse
which prevents (my simple minded attempts at) having more than one
project -- even of different types -- in the same directory tree.

MS



Kevin Klues wrote:
>     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
> Tinyos-help at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew