Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of Home › Forums › Mayfly Data Logger › best practices enabling debugging modular sensors using platformIO › Reply To: best practices enabling debugging modular sensors using platformIO
2019-08-02 at 8:04 AM
#12995
Thanks for all the information, this was very helpful. If I try to build using the following build flags,
|
1 2 3 4 5 6 |
build_flags = -DSDI12_EXTERNAL_PCINT -DNEOSWSERIAL_EXTERNAL_PCINT -DMQTT_MAX_PACKET_SIZE=240 -DMS_DATAPUBLISHERBASE_DEBUG -DMS_SODAQ2GBEER6_DEBUG |
I get the following error.
|
1 2 |
Archiving .pio\build\mayfly\libFrameworkArduino.a *** [.pio\build\mayfly\firmware.elf] Implicit dependency <code>C:\users\moist\.platformio\platforms\atmelavr\builder\this' not found, needed by target</code>.pio\build\mayfly\firmware.elf'. |
It does build without the debugging options. Maybe I should not add a second error, but if I drop the DMS_SODAQ2GBEER6_DEBUG and replace it for the DMS_THINGSPEAKPUBLISHER_DEBUG, I get a build error because of a redeclaration of ‘uint32_t start’
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
#define MS_START_DEBUG_TIMER uint32_t start = millis(); ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:214:5: note: in expansion of macro 'MS_START_DEBUG_TIMER' MS_START_DEBUG_TIMER ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src/ModSensorDebugger.h:73:39: note: 'uint32_t start' previously declared here #define MS_START_DEBUG_TIMER uint32_t start = millis(); ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:190:5: note: in expansion of macro 'MS_START_DEBUG_TIMER' MS_START_DEBUG_TIMER; ^ <command-line>:0:29: warning: ISO C++11 requires whitespace after the macro name *** [.pio\build\mayfly\libb4a\EnviroDIY_ModularSensors_ID1648\publishers\ThingSpeakPublisher.cpp.o] Error 1 |
Any help would be greatly appreciated.
