I just updated to the latest IDF and I'm getting this error: CXX build/main/ovms_module.o /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_module.cpp:40:28: fatal error: esp_heap_debug.h: No such file or directory compilation terminated. /home/ubuntu/esp/esp-idf/make/component_wrapper.mk:273: recipe for target 'ovms_module.o' failed make[1]: *** [ovms_module.o] Error 1 If I delete line 40 of ovms_module.cpp to avoid trying to import this file then everything compiles. Well it compiles if I turn off the mdns server in menuconfig. If I leave that as the sdkconfig.default.hw30 values then I get this error: CXX build/ovms_mdns/src/ovms_mdns.o In file included from /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:36:0: /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.h:48:5: error: 'mdns_server_t' does not name a type mdns_server_t *m_mdns;
Can you check ‘git branch’. Make sure you are on ‘master’ branch (not 2.1). Also make sure you’ve done the Submodule update command.
On 19 Jan 2018, at 6:58 PM, Tom Parker <tom@carrott.org> wrote:
I just updated to the latest IDF and I'm getting this error:
CXX build/main/ovms_module.o /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_module.cpp:40:28: fatal error: esp_heap_debug.h: No such file or directory compilation terminated. /home/ubuntu/esp/esp-idf/make/component_wrapper.mk:273: recipe for target 'ovms_module.o' failed make[1]: *** [ovms_module.o] Error 1
If I delete line 40 of ovms_module.cpp to avoid trying to import this file then everything compiles.
Well it compiles if I turn off the mdns server in menuconfig. If I leave that as the sdkconfig.default.hw30 values then I get this error:
CXX build/ovms_mdns/src/ovms_mdns.o In file included from /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:36:0: /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.h:48:5: error: 'mdns_server_t' does not name a type mdns_server_t *m_mdns;
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
While I assume everyone will want to follow Mark's instructions here, it was a bug that the extra include from our fork was not gated by a conditional. That is fixed now. -- Steve On Fri, 19 Jan 2018, Mark Webb-Johnson wrote:
Can you check 'git branch'. Make sure you are on 'master' branch (not 2.1).
Also make sure you've done the Submodule update command.
On 19 Jan 2018, at 6:58 PM, Tom Parker <tom@carrott.org> wrote:
I just updated to the latest IDF and I'm getting this error:
CXX build/main/ovms_module.o /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_module.cpp:40:28: fatal error: esp_heap_debug.h: No such file or directory compilation terminated. /home/ubuntu/esp/esp-idf/make/component_wrapper.mk:273: recipe for target 'ovms_module.o' failed make[1]: *** [ovms_module.o] Error 1
If I delete line 40 of ovms_module.cpp to avoid trying to import this file then everything compiles.
Well it compiles if I turn off the mdns server in menuconfig. If I leave that as the sdkconfig.default.hw30 values then I get this error:
CXX build/ovms_mdns/src/ovms_mdns.o In file included from /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:36:0: /vagrant/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.h:48:5: error: 'mdns_server_t' does not name a type mdns_server_t *m_mdns;
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
On 20/01/18 00:37, Mark Webb-Johnson wrote:
Can you check ‘git branch’. Make sure you are on ‘master’ branch (not 2.1).
I did some digging and I had ended up with the https://github.com/espressif/esp-idf.git esp-idf. Once I changed to https://github.com/openvehicles/esp-idf.git the file exists and things started compiling. There was a submodule change and I did update that. I was following the https://esp-idf.readthedocs.io/en/latest/get-started/index.html#setup-toolch... instructions to set up my toolchain, but on re-reading your mail, you were only recommedning getting the right version of the xtensa tar file not all the things! I did think it was odd that we were going back to some floating revision of the idf, but didn't actually re-check that, sorry. Is the v2 server connection over the simcom modem with the new idf reasonably stable yet?
On 20/01/18 09:45, Tom Parker wrote:
Is the v2 server connection over the simcom modem with the new idf reasonably stable yet?
Well, it works on my desk. So does an old 4gb sdcard I had lying around (I haven't tried any others), and recoding the console log to a file on the sdcard! This is a great improvement good work thank you! With the old IDF version the v2 server connection over the simcom modem was only unstable while driving, it was always solid sitting on my desk or in the car, stationary. I'll let you know how it goes when I take it for a drive.
participants (3)
-
Mark Webb-Johnson -
Stephen Casner -
Tom Parker