-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken comparison against kconfiglib.expr_value() (IDFGH-294) #2195
Comments
Hi @ulfalizer , I don't know why I didn't see this before now. Thanks so much, your observation is of course 100% correct! Fix incoming soon. (Still haven't forgotten about updating to upstream kconfiglib as well - but also haven't had time to do so :|.) |
No worries! If you want to quickly try out the No obligation though. I realize you have lots of stuff to do. diff --git a/Kconfig b/Kconfig
index 75815ba1a..8bc9a2ac2 100644
--- a/Kconfig
+++ b/Kconfig
@@ -56,7 +56,7 @@ mainmenu "Espressif IoT Development Framework Configuration"
endmenu # SDK tool configuration
- source "$COMPONENT_KCONFIGS_PROJBUILD"
+ #source "$COMPONENT_KCONFIGS_PROJBUILD"
menu "Compiler options"
@@ -203,5 +203,5 @@ mainmenu "Espressif IoT Development Framework Configuration"
endmenu # Compiler Options
menu "Component config"
- source "$COMPONENT_KCONFIGS"
+ #source "$COMPONENT_KCONFIGS"
endmenu |
When generating JSON metadata for ranges where there are conditional ranges (ie different allowed range depending on another config setting), the JSON metadata would always have the last named range as the expression was not evaluated properly. Thanks to ulfalizer on GitHub for pointing this out. Closes #2195
When generating JSON metadata for ranges where there are conditional ranges (ie different allowed range depending on another config setting), the JSON metadata would always have the last named range as the expression was not evaluated properly. Thanks to ulfalizer on GitHub for pointing this out. Closes #2195
When generating JSON metadata for ranges where there are conditional ranges (ie different allowed range depending on another config setting), the JSON metadata would always have the last named range as the expression was not evaluated properly. Thanks to ulfalizer on GitHub for pointing this out. Closes espressif/esp-idf#2195
When generating JSON metadata for ranges where there are conditional ranges (ie different allowed range depending on another config setting), the JSON metadata would always have the last named range as the expression was not evaluated properly. Thanks to ulfalizer on GitHub for pointing this out. Closes espressif/esp-idf#2195
Hello,
Stumbled upon this when browsing the code a bit:
esp-idf/tools/kconfig_new/confgen.py
Line 217 in e7faa1d
expr_value()
returns a 0/1/2 tristate value, so will need to be e.g. this instead:Similarly here too:
esp-idf/tools/kconfig_new/confgen.py
Line 228 in e7faa1d
And yeah, that 0/1/2 vs. n/m/y thing is a bit confusing. It simplifies comparisons and streamlines the implementation a bit at least.
Cheers,
Ulf
The text was updated successfully, but these errors were encountered: