Skip to content

Compile errors when using Particle Build #4

Open
@kaliatech

Description

@kaliatech

There are two code issues in this library source that result in compilation errors if copy/pasted in to the Particle Build cloud IDE. I am not familiar enough with the Particle ecosystem and history to understand if/how this worked previously.

Compile errors:

src/SparkFunRHT03.cpp:119:28: error: 'CHECKSUM' was not declared in this scope
     if (checksum(dataBytes[CHECKSUM], dataBytes, 4))
                            ^
src/SparkFunRHT03.cpp:121:48: error: 'HUMIDITY_H' was not declared in this scope
   _humidity = (static_cast<uint16_t>(dataBytes[HUMIDITY_H] << 8) | dataBytes[HUMIDITY_L]);
                                                ^
src/SparkFunRHT03.cpp:121:78: error: 'HUMIDITY_L' was not declared in this scope
   _humidity = (static_cast<uint16_t>(dataBytes[HUMIDITY_H] << 8) | dataBytes[HUMIDITY_L]);
                                                                              ^
src/SparkFunRHT03.cpp:122:52: error: 'TEMP_H' was not declared in this scope
   _temperature = static_cast<uint16_t> ((dataBytes[TEMP_H] << 8) | dataBytes[TEMP_L]);
                                                    ^
src/SparkFunRHT03.cpp:122:78: error: 'TEMP_L' was not declared in this scope
   _temperature = static_cast<uint16_t> ((dataBytes[TEMP_H] << 8) | dataBytes[TEMP_L]);
                                                                              ^
src/SparkFunRHT03.cpp:131:6: error:
prototype for 'bool RHT03::checksum(byte, const byte*, unsigned int)' 
does not match any in class 'RHT03'
 bool RHT03::checksum(const byte check, const byte * data, const unsigned int datalen)
      
src/SparkFunRHT03.cpp:35:7: error: candidate is: bool RHT03::checksum(byte, byte*, unsigned int)
  bool checksum(byte check, byte * data, const unsigned int datalen);       

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions