esp32: make bootloader is not working for building from the source code about nuttx

[acassis]

@tmedicci any idea?

[tmedicci]

Hi @acassis !

I tested it locally (and our internal CI also tests it daily). I could not find any problems. I suspect this is somehow related to the outdated kconfig-frontends, but I was not even able to build it locally (it requires very old libraries). Can you check with kconfiglib?

[acassis]

Thank you @tmedicci actually this issue was reported by @casaroli and I just tried to reproduced the issue. I think he is used kconfiglib, but if this is some issue caused by Kconfig, it should be modified to work with kconfig-frontends and kconfiglib.

[tmedicci]

@acassis and @casaroli , the bootloader built from the sources uses a wrapper around an IDF-provided repository (the esp-nuttx-bootloader). Kconfiglib is a dependency of ESP-IDF, so it must be installed (not by NuttX, but for esp-nuttx-bootloader). This is why we are removing support for the IDF's bootloader.

NuttX adopted kconfiglib later and it uses it by default. This required users that still want to use kconfig-frontends to uninstall kconfiglib (or, equivalently, uninstall for their python environment): this is why this problem has risen.

I'm closing this issue because IDF's bootloader is about to be deprecated. I recommend keeping kconfiglib installed to enable building the bootloader from the sources. There are a list of possible workarounds to be used (if kconfig-frontends is required) until we completely deprecate the use of the IDF's bootloader:

• Install kconfiglib in a python environment and activate/deactivate it before/after running make bootloader;
• Modify NuttX's build system to enable selecting a preferred tool (instead of using kconfiglib by default, when available).

[acassis]

Thank you very much for this explanation @tmedicci !

Actually kconfiglib is not the default option for NuttX, it is optional: https://nuttx.apache.org/docs/latest/quickstart/install.html

I think both kconfig-frontends and kconfiglib work correctly in the NuttX building system, I wasn't aware of this limitation/constraints of ESP-IDF. Thank you again for above explanation.

[tmedicci]

You're welcome, Alan!

Actually kconfiglib is not the default option for NuttX, it is optional:
https://nuttx.apache.org/docs/latest/quickstart/install.html

I meant that, if available, kconfiglib will be used instead of kconfig-frontends:

nuttx/tools/Unix.mk

Line 639 in cfa5443

# Prefer "kconfiglib" if host OS supports it