<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Kconfiglib.git/kconfiglib.py, branch v9.4.0</title>
<subtitle>Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git</subtitle>
<id>https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.4.0</id>
<link rel='self' href='https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.4.0'/>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/'/>
<updated>2018-08-11T02:20:53Z</updated>
<entry>
<title>Don't pass encoding= to Popen()</title>
<updated>2018-08-11T02:20:53Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-11T00:54:27Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=6aea8d06b637ea55a2fa7d2949863adae5310ce2'/>
<id>urn:sha1:6aea8d06b637ea55a2fa7d2949863adae5310ce2</id>
<content type='text'>
Popen()'s 'encoding' parameter is Python 3.6+ only.

Unfortunately, Popen()'s universal_newlines=True without 'encoding' will
use the encoding from the environment. Do a manual version instead, so
that we can still use the user-specified encoding (usually UTF-8). That
might prevent problems on systems that are (poorly) configured to use
the C locale.
</content>
</entry>
<entry>
<title>Improve naming in the custom expr. printing functions</title>
<updated>2018-08-10T04:39:22Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-10T04:23:53Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=d0732cff9cef507d79d5c53fbcc648dd6f560ce5'/>
<id>urn:sha1:d0732cff9cef507d79d5c53fbcc648dd6f560ce5</id>
<content type='text'>
 - *_fn() prefixes on functions are a bit silly. It makes more sense for
   the expr_str() parameter, so keep it there.

 - Use *_expr_str() instead of just *_str(), to make it clearer that
   these deal with expressions.
</content>
</entry>
<entry>
<title>Support custom printing of symbols/choices in expressions</title>
<updated>2018-08-10T02:57:13Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-09T22:04:12Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=1f864b104a1f64b1c72ab13422070f6ad7cad225'/>
<id>urn:sha1:1f864b104a1f64b1c72ab13422070f6ad7cad225</id>
<content type='text'>
Allow custom output formats for symbols/choices when turning expressions
into strings, via a user-supplied callback function (sc_str_fn).

This makes things like turning symbols into links in generated
documentation and displaying symbol values in the menuconfig interface
less hacky to implement.

Two new Symbol/Choice.custom_str() functions were added, as passing
extra arguments to __str__() is awkward.
</content>
</entry>
<entry>
<title>Look for '$(' instead of '$' for inline macro expansions</title>
<updated>2018-07-31T21:54:19Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-31T11:33:52Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=9cf4bd2310bb1d1de4cc199b1a0ad9ba7d87e3ae'/>
<id>urn:sha1:9cf4bd2310bb1d1de4cc199b1a0ad9ba7d87e3ae</id>
<content type='text'>
This gives a less confusing KconfigError message for syntax errors like
'config $FOO'.
</content>
</entry>
<entry>
<title>Restore compatibility with old kernels</title>
<updated>2018-07-24T20:13:43Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-24T20:13:43Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=6899f91867ecd1df50620499db7a64f9d5c1397b'/>
<id>urn:sha1:6899f91867ecd1df50620499db7a64f9d5c1397b</id>
<content type='text'>
Add a small hack to restore compatibility with older (2015-) versions of
the Linux kernel. Weird help tokens like -help- and --help--- are now
accepted again.

Compatibility was originally dropped by commit c19fc11 ("Drop some
compatibility and tighten up lexing"), but it turns that people are
still using Kconfiglib with older kernels.

The new compatibility hack has pretty minimal impact at least.
</content>
</entry>
<entry>
<title>Use universal newlines mode in $(shell) implementation</title>
<updated>2018-07-24T20:06:28Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-24T17:50:15Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=b650ccda72102bf8581420cfa31f6c6eab67f65d'/>
<id>urn:sha1:b650ccda72102bf8581420cfa31f6c6eab67f65d</id>
<content type='text'>
This prevents e.g. stray \r's in command output on Windows after
stripping trailing newlines.
</content>
</entry>
<entry>
<title>Fix detection of hex literals</title>
<updated>2018-07-20T20:09:51Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-20T20:03:43Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=2d391d8f369a40b438a1b246c888bb42b2e14278'/>
<id>urn:sha1:2d391d8f369a40b438a1b246c888bb42b2e14278</id>
<content type='text'>
Missing 'not'. Add some literals to the Kstrict testcase.
</content>
</entry>
<entry>
<title>Mention KCONFIG_STRICT in the README</title>
<updated>2018-07-20T19:32:24Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-20T19:31:00Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=ec57b1f3da0f0e2f348574a11a62b2c2c58cec42'/>
<id>urn:sha1:ec57b1f3da0f0e2f348574a11a62b2c2c58cec42</id>
<content type='text'>
Also fix up Kconfig.__init__() docstring to say that KCONFIG_STRICT
needs to be "y".
</content>
</entry>
<entry>
<title>Add KCONFIG_STRICT flag for flagging refs. to undefined syms</title>
<updated>2018-07-20T19:15:23Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-20T02:14:31Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=ca89d02ca1639b72c7b74834ff432ab10df58fe9'/>
<id>urn:sha1:ca89d02ca1639b72c7b74834ff432ab10df58fe9</id>
<content type='text'>
Settings KCONFIG_STRICT to y in the environment turns on warnings for
all references to undefined symbols within Kconfig files (with the only
gotcha that hex literals must be prefixed by 0x or 0X, to make it
possible to distinguish them from undefined references).

Always flagging undefined references gets awkward, as some projects
(e.g. the Linux kernel) use multiple Kconfig trees with shared files,
leading to some safe undefined references. It's helpful for other
projects though.

Having KCONFIG_STRICT as an environment variable is handy when multiple
tools are involved.

Piggyback a small README change re. warnings. Kconfiglib now has many
more warnings than the C tools.
</content>
</entry>
<entry>
<title>Simplify self.srctree assignment</title>
<updated>2018-07-20T01:20:30Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-07-20T01:20:30Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=ccb18af3419b72ef4ddc5f311abebebd858a36ce'/>
<id>urn:sha1:ccb18af3419b72ef4ddc5f311abebebd858a36ce</id>
<content type='text'>
</content>
</entry>
</feed>
