Menuconfig is not saved about esp32-arduino-lib-builder HOT 7 CLOSED

After discussion with @me-no-dev the propper way is to modify esp32-arduino-lib-builder/configs/defconfig.common

In that case, what's the point of the command: ./build.sh -t esp32 -b menuconfig, if my have to manually edit esp32-arduino-lib-builder/configs/defconfig.common????

from esp32-arduino-lib-builder.

Same problem.

from esp32-arduino-lib-builder.

After discussion with @me-no-dev the propper way is to modify esp32-arduino-lib-builder/configs/defconfig.common
See espressif/arduino-esp32#7193

from esp32-arduino-lib-builder.

what's the point of the command ./build.sh -t esp32 -b menuconfig:

Maybe @me-no-dev can answer that.

from esp32-arduino-lib-builder.

After discussion with @me-no-dev the propper way is to modify esp32-arduino-lib-builder/configs/defconfig.common

In that case, what's the point of the command: ./build.sh -t esp32 -b menuconfig, if my have to manually edit esp32-arduino-lib-builder/configs/defconfig.common????

For some params you have default values, which will overwrite the values you set, but not all. The point is to have default values for espressif build make it easier. If you want to change some value which exist in default.xxx you just have to remove it or comment out in default.xxx file.

It is rare case when users edit values in menuconfig, but its common case (CI) when its required to use default values.
Sure, its not optimal, but i think the only option with Smake to do it, but i may be wrong (not cmake expert).

from esp32-arduino-lib-builder.

Seems like the rather sparse README.md should be updated to note this. I just wasted 2 hours trying to figure out why trying to enable the FreeRTOS trace facility via the CONFIG_FREERTOS_USE_TRACE_FACILITY in sdkconfig was just getting tossed out like a piece of old dead fish, only to find it in a closed issue.

It's very counterintuitive to have to modify files in esp32-arduino-lib-builder/configs when ESP-32 developers (and people with a Linux kernel background) are used to using menuconfig.

The real issue is that changes to sdkconfig are being thrown away, rather than just having whatever values are specified in the defaults files overwriting those particular settings in the sdkconfig

from esp32-arduino-lib-builder.

menuconfig and sdkconfig relate only to certain configuration/chip at once. Here we build for all supported chips. The ./build.sh -t [chip] menuconfig in intended to configure a normal project build for particular chip only and not to relate that to building and exporting libraries to Arduino. Imagine it as you using the repo to build your own firmware for particular board that uses Arduino as component.

from esp32-arduino-lib-builder.