Philip Levis wrote:
>I'd be all for a mechanism that can solve the general case, but am leery of
>adding a special case like this.
Phil
==========
Kevin Klues wrote:
> Add this environment variable to the .profile file (or wherever environment
> variables are set up):
> export TOSCONTRIB=/path/to/tinyos-2.x-contrib
>
> in the .platform file do
>
> $ecosensdir = "$ENV{TOSCONTRIB}/ecosenys"
> push( @includes, qw(
>
> $ecosensdir/platforms/ecosens1
==============
> push( @includes, qw(
>
> %P/chips/stm25p
> %P/chips/cc2420
>
> %T/chips/cc2420
> %T/chips/cc2420/alarm
> ...
>
> as %P is replaced by the directory of the .platform file... Note that
> this does assume you're eventually invoking ncc something like this:
> ncc -I$TOSCONTRIB/ecosens1 -target=ecosens1 <other options and files>
>
> David
====================
This reduces a hurdle to my customers in using code in contrib,
and makes it simpler and partly self documenting. If we add any complexity,
we should be removing 2X the complexity elsewhere.
What makes the .platform file necessary separately from the ecosens1.target
file? Could the ecosens1.target do it all somehow?
John Griessen
--
Ecosensory
tinyOS devel on: ubuntu Linux; tinyOS v2.0.2; telosb ecosens1
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
