[Ovmsdev] Scripting: Duktape update to version 2.5.0

Craig Leres leres at xse.com
Sat Jan 4 10:02:05 HKT 2020

On 2020-01-02 11:13, Craig Leres wrote:
> Ah, I found something. At the start of a clean build (rm -rf build && 
> gmake -j8):
>      ice 509 % gmake -j8
>      gmake: gcc: Command not found
>      expr: syntax error
>      #
>      # configuration written to 
> /home/ice/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/sdkconfig 
> This seems familiar but I can't figure out where "gcc" is hardcoded. 
> Even when I use "gmake -j8 CC=gcc9" I don't get a dialog to add missing 
> things to my sdkconfig. It looks like even "gmake defconfig" is a noop.

Wow that was hard to find. The problem is esp-idf/make/project.mk has 
this bit of clever hardcoding:

     # Set target compiler. Defaults to whatever the user has
     # configured as prefix + ye olde gcc commands
     CC := $(call dequote,$(CONFIG_TOOLPREFIX))gcc

If you don't have gcc, everything breaks with a warning. Here's the pull 


I believe this can get called two ways. One is when building 
esp-idf/tools/kconfig when CONFIG_TOOLPREFIX is not set (CC is set to 
gcc) and the other is when we're cross compiling (CC is set to 

I'm not in love with fixing it here but when I tried to do it in 
OVMS.V3/Makefile after $(IDF_PATH)/make/project.mk is included it 
doesn't take effect when building kconfig. Lemme know if you can think 
of another way to solve this. But it does prompt me for new sdkconfig 
options again.

BTW I've verified that I can build with CONFIG_MG_ENABLE_SSL but am 
running with something close to support/sdkconfig.default.hw31.


More information about the OvmsDev mailing list