| Age | Commit message (Collapse) | Author |
|---|
|
Adds commit 4602028 ("genconfig: Allow writing a full .config without
incremental build info"), which adds a flag to genconfig that might be
handy in projects that include .config files in Makefiles but that don't
use incremental build information.
|
|
For projects that don't use incremental build information, it's a bit
wasteful to generate it just to get an updated .config file to include
in Makefiles. Add a '--config-out <filename>' option that just writes
the updated .config file, for those cases.
Also remove a redundant default=None argument for --sync-deps. None is
the default value.
|
|
|
|
Just adds commit 4af2ac3 ("Actually fix README RST display on PyPI").
|
|
Use anonymous hyperlinks to avoid having two links named 'Kconfig', like
in commit fe28703 ("Fix README RST display on PyPI").
|
|
Just adds commit fe28703 ("Fix README RST display on PyPI").
|
|
Use anonymous hyperlinks to avoid having two links named 'here', which
RST apparently doesn't like.
Related:
https://stackoverflow.com/questions/5464627/how-to-have-same-text-in-two-links-with-restructured-text/14067756
|
|
Gets the README updated from commit 534e3e7 ("Add a 'getting started'
section to the README") up on PyPI.
|
|
|
|
|
|
Might make it clearer how the different parts fit together.
Also mention that deps/auto.conf can be used as Make input, and that it's
preferable to using .config. This is hard to discover on your own.
|
|
Adds commit 21e47ce ("Fix parse error message on the line after help
texts"), which fixes incorrect line contents being reported for parse
errors on the line after a help text.
|
|
The correct error and line number was reported, but not the correct line
contents. self._line needs to be set before calling _tokenize(), so that
_parse_error() knows the context.
There's no need to set self._line for empty lines, because we
immediately end up back in _next_line() after parsing the help text,
which refetches the empty line and updates self._line.
|
|
|
|
|
|
|
|
Adds some documentation nits:
- 08abf44 ("Mention that pydoc works after installing with pip")
- 6aaf01c ("Clean up documentation a bit re. named choice")
- 6fe5198 ("menuconfig: Mark quit_dialog() as internal")
|
|
Also mention that menuconfig.py has documentation.
|
|
Zephyr uses several named choices, and I've seen them in other projects
now too, so don't imply that they aren't used. The menuconfig interface
now has better support for them than the C tools too, where adding
symbols by defining a choice in multiple locations is broken.
Also remove a reference to Kconfiglib 1.
|
|
Oversight. The _ hides it from e.g. pydoc.
|
|
|
|
Adds commit 43e7711 ("setup: Use a list instead of a tuple for
'classifiers'"), which fixes a setup.py issue on Python 3.7.
|
|
Fixes a warning on Python 3.7:
Warning: 'classifiers' should be a list, got type 'tuple'
Maybe it could prevent other issues too:
https://github.com/pypa/pypi-legacy/issues/670
|
|
Adds commit 3b692df ("olddefconfig: Add script"), which bundles a new
script that mimics 'make olddefconfig'. This could also be accomplished
by entering the menuconfig interface and saving, but its more awkward.
Some minor internal documentation clarifications and cleanups are
included as well:
- Commit 53db3ee ("Clarify node_iter() documentation re. iteration order")
- Commit c1dcaa3 ("Refactor parsing to get rid of _saved_line")
- Commit 6aab113 ("Don't set filename and linenr on 'if' menu nodes")
|
|
Works like 'make olddefconfig', updating a configuration by filling in
default values for all new symbols.
This could also be accomplished by entering the 'menuconfig' interface
and saving the configuration, but it's more awkward and less obvious.
Piggyback two oldconfig changes:
- Mention KCONFIG_CONFIG
- Check if the .config file exists before parsing the Kconfig files,
instead of after
|
|
There's no way to query them later, as 'if's get flattened and removed,
and they're not needed during parsing either.
|
|
The old version might not have made it obvious that a node is visited
before its children.
|
|
Handle the line-after-help-text case specially, which allows _has_tokens
(renamed to _reuse_tokens) to be used as the unget mechanism for help
texts as well, leaving _saved_line unused. Move the _reuse_tokens check
into _next_line().
This makes _parse_block() as straightforward as _parse_properties(), and
simplifies _parse_properties() a tiny bit too by getting rid of the
'_tokens_i = -1' assignment.
|
|
Consistently indent with tabs, like in the actual output.
|
|
Do the PEP 8 ordering thingy with standard library imports first.
|
|
Style nits.
|
|
|
|
Adds commit c91e17c ("Give clearer errors for bad
endchoice/endif/endmenu nesting"). Previously, an
endchoice/endif/endmenu without a corresponding choice/if/menu generated
a cryptic "unrecognized construct" error.
|
|
Easier to read.
|
|
An endchoice/endif/endmenu with no corresponding choice/if/menu
generated a cryptic 'unrecognized construct' parse error. Improve the
error message so that the problem is pointed out explicitly:
kconfiglib.KconfigError: Kconfig:37: couldn't parse 'endmenu': no corresponding 'menu'
Reported in https://github.com/ulfalizer/Kconfiglib/issues/56.
|
|
|
|
|
|
Adds support for user-defined preprocessor functions in Python, which
can be used to get information from existing Python tools into Kconfig,
e.g. to have Kconfig symbols depend on hardware information stored in
some other format.
See commit b6827ca ("Add support for user-defined Python preprocessor
functions").
|
|
Allow preprocessor functions to be defined in Python by putting a module
called 'kconfigfunctions' into sys.path. Internally, this simply adds
the functions to the predefined functions in Kconfig._functions.
User-defined Python functions make it simple to integrate information
from existing Python tools into Kconfig, e.g. to have Kconfig symbols
depend on hardware information stored in some other format. This might
be used to get device tree information into Kconfig in Zephyr.
Piggyback module docstring documentation for some extensions that were
previously only mentioned in the README.
|
|
- Remove some unused imports
- Replace a lambda with a plain function
- Shorten some long lines
- Remove some redundant backslashes within brackets
|
|
Also remove some redundant backslashes within brackets.
|
|
Simplifies the code. Should promote new APIs.
Also fix list_undefined.py for recent kernels. More environment
variables are referenced now.
|
|
No idea where "menu." came from.
|
|
Adds commit b9b2ebb ("menuconfig: Add RGB color support to styles."),
which makes it possible to specify colors in MENUCONFIG_STYLE
using #RRGGBB notation.
The rendered colors may be more or less exact depending on terminal
capabilities. In the best case, we can redefine colors. Otherwise, we
fall back on the closest available color.
Contributed by Mitja Horvat (punkfluid).
|
|
- Point out where the styling part starts and ends
- Move _style_attr() into the styling part (by moving the comment)
- Move _name_and_val_str() and _expr_str() to later in the file, closer
to where they're used (mostly in the help dialog)
- Turn _input_dialog() input handling into one if-elif-... chain, like
for the other dialogs.
|
|
Prevent the 'Symbol/choice/menu/comment information' title string from
disappearing when it won't fit on the terminal.
Piggyback some code nits:
- Remove a redundant 'global _style'
- Use 'elif' after checking for KEY_RESIZE
- Consistently use '_sel_node_i = _menu_scroll = 0' to reset positions,
e.g. when entering menus
|
|
- Make the coding style a bit more consistent with the rest of the code
- Allow colors to be allocated from the xterm 256-color grayscale
range, and emulate it when dynamically allocating colors. Never
allocate above color number 255 though, as anything there would be
unknown territory.
- Switch back to consistently passing tuples to functions. This was the
original design, before I suggested changing it...
- Remove some repeated information from docstrings and fix some small
typos
- Make use of the element1=element2 feature in the style definition
for the 'default' style
|
|
Styles can now take a HTML notation as a color value:
- on terminals that support RGB color mode these are rendered
perfeclty
- on 256 color terminals the closes matching color is used
- on other terminals, the current color palette is scanned
and the closes matching color is used. This has few quirks
Example: Use "pure" red as selection foreground and "pure" blue as
background:
MENUCONFIG_STYLE="selection=fg:#ff0000,bg:#0000ff"
Additionally, it is possible to copy the style from other elements,
for example:
MENUCONFIG_STYLE="selection=fg:#ff0000,bg:#0000ff path=selection"
In the notation above, the "path" style will be copied from "selection".
|
|
Adds commit af6c8dc ("menuconfig: Fix some glitching on small
terminals"), which fixes some minor graphical glitching in the
menuconfig interface when the terminal is too small for things to fit.
Commit 374f488 ("Clean up kernel Makefile patch and add new targets")
adds some new targets to the Linux makefile patch as well, though the
makefile patch isn't bundled on PyPI.
|
|
|
