-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Feature request: Machine-readable description of build config options #2989
Comments
Progess: I compiled short descriptions for all documented modules. Preparations for categorization. |
That sounds like a good idea. There is also a possible related issue #386 . |
Can you/someone estimate how far away that future is? |
Cool, who is working on that? It's the first time I hear this. I was also going to propose to @mk-pmb that before he reinvents the wheel he should look into what ESP-IDF does with Kconfig. |
I tried to find where I read it but can't. Seems that I didn't read close enough. It is between #1657 (comment) and a testrun to integrate and build the two variants in one repo by someone (don't remember who) that I got that impression. |
This came up in some discussion between Johny and me, but ATM @jmattsson has even less bandwidth on NodeMCU than I do. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Any news on this? |
It's still on my todo list, just like last year >.<
…On Sun, 31 Jan 2021 at 17:18, M.K. ***@***.***> wrote:
Any news on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2989 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGUJZ4LWCFTEMJ6K2BFRXDS4TYZRANCNFSM4KBWVZUA>
.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is anyone still working on this, or has it on their todo? |
Missing feature
Let's make the comments in
app/include/user_*.h
more machine-readable:In case we already have such info, let's put a hint where to find it on top of the header files. And establish a mechanism for keeping them in sync.
Justification
I'd like to make a config wizard. That wizard, at a minimum, should be able to determine whether it's understanding of available options is still compatible with the currently checked-out version of the firmware. Would be nice if it could also fall back to the maintainer's help texts if it cannot find localized/optimized help texts from a user-preferred source.
Workarounds
If it turns out we don't have such info, I might have to bake my own.
The text was updated successfully, but these errors were encountered: