The doc/tutorial describes how to do this with the "config" file.
For a simple example, I think the Blink demo app has a config
file that links in a couple of external modules. Or look for
an app that has multiple .nc files (in T1 SimpleCmd has more
than one source file) and see how it works.
MS
Jude Allister wrote:
> I have created a module that provides 3 interfaces. It is called
> "LEDModuleC.nc" and it includes a .h file containing things that module
> needs.
>
> I am having trouble testing it in a different application now. Is there
> a specific file-name format I must give it instead of LEDModuleC.nc?
> How do I tell my test application where to find it? Do I just #include
> "LEDModuleC.nc" ??
>
> I was under the impression that if I put them all in the same folder,
> the "uses" statements in the test application would make nesC look for
> the stuff in LEDModuleC.nc. I guess this isn't the case?
>
>
> also, I am a bit confused either way about what would go in my
> TestAppC.nc and TestC.nc files to use the new module. I looked at a bit
> of the TinyOS examples/library files and I'm still not quite getting it.
>
> Right now:
>
> TestC.nc:
> // 3 interfaces provided by LEDModuleC.nc
> uses interface LEDCycler;
> uses interface LEDBlinker;
> uses interface LEDPulser;
>
> TestAppC.nc
>
> // can't exactly figure this part out.
>
>
> Hopefully this is something quick/minor to work out.
>
> Thank you
>
>
>
>
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
