Actually, don't mind my last message. It was a makefile problem. I added the line 
PFLAGS=-I%T/lib/Counters and everything worked out fine (even my code!).

- Thiago

----- Original Message -----
From: THIAGO TEIXEIRA <[EMAIL PROTECTED]>
Date: Tuesday, December 9, 2003 1:32 pm
Subject: Fwd: Strange compile problems

> Hi, I'm building a sensorboard and, as a first step, made a 
> sensorboard.h file. To make sure it's working, I created a simple 
> application called CamRead that should just get an integer from 
> port F in the mica2 (using a little app called PortRead that I 
> wrote) and display it on the Leds (using IntToLeds). It looks like 
> this:
> 
> configuration CamRead {
> }
> implementation {
> components Main, PortRead, IntToLeds;
> 
> Main.StdControl -> IntToLeds.StdControl;
> Main.StdControl -> PortRead.StdControl;
> 
> PortRead.IntOutput -> IntToLeds.IntOutput;
> 
> }
> 
> when I compile it, I get the following error:
> 
> CamRead.nc:5: component IntToLeds not found
> C:/PROGRA~1/tinyos/cygwin/opt/tinyos-
> 1.x/tos/sensorboards/camb/PortRead.nc:3: expected component 
> `IntToLeds', but got component 'PortRead'
> CamRead.nc:7: cannot find `StdControl'
> CamRead.nc:10: cannot find `IntOutput'
> make: *** [build/mica2/main.exe] Error 1
> 
> but if I change the order of the components declaration to Main, 
> IntToLeds, PortRead, I get:
> 
> CamRead.nc:5: component IntToLeds not found
> C:/PROGRA~1/tinyos/cygwin/opt/tinyos-
> 1.x/tos/platform/avrmote/HPLInit.nc:51: expected component 
> `IntToLeds', but got component 'HPLInit'
> CamRead.nc:7: cannot find `StdControl'
> CamRead.nc:10: cannot find `IntOutput'
> make: *** [build/mica2/main.exe] Error 1
> 
> I thought it was a $TOSDIR problem, but when I enter $TOSDIR at 
> the prompt I get "bash: /opt/tinyos-1.x/tos: is a directory". So, 
> it seems to be ok.
> 
> What's going on here?
> 
> 
> - Thiago
> 

_______________________________________________
Tinyos-users mailing list
[EMAIL PROTECTED]
http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users

Reply via email to