meshtastic / firmware

Meshtastic device firmware
https://meshtastic.org
GNU General Public License v3.0
3k stars 719 forks source link

Compilation errors after pulling the new version #103

Closed SensorsIot closed 4 years ago

SensorsIot commented 4 years ago

I tried to build a version for the beam and got these errors:

Building in release mode Compiling .pio\build\tbeam\src\rf95\CustomRF95.cpp.o Compiling .pio\build\tbeam\src\rf95\RH_RF95.cpp.o Compiling .pio\build\tbeam\src\sleep.cpp.o Generating partitions .pio\build\tbeam\partitions.bin Compiling .pio\build\tbeam\lib9b7\Wire\Wire.cpp.o Compiling .pio\build\tbeam\libf31\SPI\SPI.cpp.o Compiling .pio\build\tbeam\lib178\ESP8266_SSD1306\OLEDDisplay.cpp.o Compiling .pio\build\tbeam\lib178\ESP8266_SSD1306\OLEDDisplayUi.cpp.o Compiling .pio\build\tbeam\lib01c\CRC32_ID1202\CRC32.cpp.o src\rf95\CustomRF95.cpp: In member function 'virtual void CustomRF95::loop()': src\rf95\CustomRF95.cpp:191:5: error: 'loop' is not a member of 'RH_RF95' RH_RF95::loop(); ^ Compiling .pio\build\tbeam\libea2\arduino-fsm\Fsm.cpp.o src\rf95\RH_RF95.cpp: In member function 'virtual bool RH_RF95::init()': src\rf95\RH_RF95.cpp:114:28: error: 'enableInterrupt' was not declared in this scope return enableInterrupt(); ^ src\rf95\RH_RF95.cpp: At global scope: src\rf95\RH_RF95.cpp:117:31: error: no 'bool RH_RF95::enableInterrupt()' member function declared in class 'RH_RF95' bool RH_RF95::enableInterrupt() ^ src\rf95\RH_RF95.cpp:136:50: error: no 'void RH_RF95::disableInterrupt()' member function declared in class 'RH_RF95' void RH_INTERRUPT_ATTR RH_RF95::disableInterrupt() ^ src\rf95\RH_RF95.cpp:159:55: error: no 'void RH_RF95::handleInterruptLevel0()' member function declared in class 'RH_RF95' void RH_INTERRUPT_ATTR RH_RF95::handleInterruptLevel0() ^ src\rf95\RH_RF95.cpp: In member function 'virtual void RH_RF95::handleInterrupt()': src\rf95\RH_RF95.cpp:246:21: error: 'enableInterrupt' was not declared in this scope enableInterrupt(); // Let ISR run again ^ src\rf95\RH_RF95.cpp: At global scope: src\rf95\RH_RF95.cpp:249:20: error: no 'void RH_RF95::loop()' member function declared in class 'RH_RF95' void RH_RF95::loop() ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr0()': src\rf95\RH_RF95.cpp:263:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[0]->handleInterruptLevel0(); ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr1()': src\rf95\RH_RF95.cpp:268:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[1]->handleInterruptLevel0(); ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr2()': src\rf95\RH_RF95.cpp:273:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[2]->handleInterruptLevel0();

geeksville commented 4 years ago

oh yes. I posted on the forum about this, but platformio seems to have a bug with removing dependencies on libraries. I removed a dependency on radiohead, but it is still trying to build against it.

To fix: delete the .pio directory in your source tree. Platform IO uses that directory as a cache and if it is missing they will refetch/regen everything they need.

On Tue, Apr 21, 2020 at 12:18 AM SensorsIOT notifications@github.com wrote:

I tried to build a version for the beam and got these errors:

Building in release mode Compiling .pio\build\tbeam\src\rf95\CustomRF95.cpp.o Compiling .pio\build\tbeam\src\rf95\RH_RF95.cpp.o Compiling .pio\build\tbeam\src\sleep.cpp.o Generating partitions .pio\build\tbeam\partitions.bin Compiling .pio\build\tbeam\lib9b7\Wire\Wire.cpp.o Compiling .pio\build\tbeam\libf31\SPI\SPI.cpp.o Compiling .pio\build\tbeam\lib178\ESP8266_SSD1306\OLEDDisplay.cpp.o Compiling .pio\build\tbeam\lib178\ESP8266_SSD1306\OLEDDisplayUi.cpp.o Compiling .pio\build\tbeam\lib01c\CRC32_ID1202\CRC32.cpp.o src\rf95\CustomRF95.cpp: In member function 'virtual void CustomRF95::loop()': src\rf95\CustomRF95.cpp:191:5: error: 'loop' is not a member of 'RH_RF95' RH_RF95::loop(); ^ Compiling .pio\build\tbeam\libea2\arduino-fsm\Fsm.cpp.o src\rf95\RH_RF95.cpp: In member function 'virtual bool RH_RF95::init()': src\rf95\RH_RF95.cpp:114:28: error: 'enableInterrupt' was not declared in this scope return enableInterrupt(); ^ src\rf95\RH_RF95.cpp: At global scope: src\rf95\RH_RF95.cpp:117:31: error: no 'bool RH_RF95::enableInterrupt()' member function declared in class 'RH_RF95' bool RH_RF95::enableInterrupt() ^ src\rf95\RH_RF95.cpp:136:50: error: no 'void RH_RF95::disableInterrupt()' member function declared in class 'RH_RF95' void RH_INTERRUPT_ATTR RH_RF95::disableInterrupt() ^ src\rf95\RH_RF95.cpp:159:55: error: no 'void RH_RF95::handleInterruptLevel0()' member function declared in class 'RH_RF95' void RH_INTERRUPT_ATTR RH_RF95::handleInterruptLevel0() ^ src\rf95\RH_RF95.cpp: In member function 'virtual void RH_RF95::handleInterrupt()': src\rf95\RH_RF95.cpp:246:21: error: 'enableInterrupt' was not declared in this scope enableInterrupt(); // Let ISR run again ^ src\rf95\RH_RF95.cpp: At global scope: src\rf95\RH_RF95.cpp:249:20: error: no 'void RH_RF95::loop()' member function declared in class 'RH_RF95' void RH_RF95::loop() ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr0()': src\rf95\RH_RF95.cpp:263:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[0]->handleInterruptLevel0(); ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr1()': src\rf95\RH_RF95.cpp:268:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[1]->handleInterruptLevel0(); ^ src\rf95\RH_RF95.cpp: In static member function 'static void RH_RF95::isr2()': src\rf95\RH_RF95.cpp:273:33: error: 'class RH_RF95' has no member named 'handleInterruptLevel0' _deviceForInterrupt[2]->handleInterruptLevel0();

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/meshtastic/Meshtastic-esp32/issues/103, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABXB2ON7AOJYK37VQVLC3TRNVCCLANCNFSM4MNBY3KA .

geeksville commented 4 years ago

(I think this should fix it - if not please reopen bug)