<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Kconfiglib.git/kconfiglib.py, branch v9.4.2</title>
<subtitle>Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git</subtitle>
<id>https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.4.2</id>
<link rel='self' href='https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v9.4.2'/>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/'/>
<updated>2018-08-17T23:10:41Z</updated>
<entry>
<title>Revert "Fix $srctree logic for the top-level Kconfig file"</title>
<updated>2018-08-17T23:10:41Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-17T23:07:23Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=df97bcaea2d6c24ddd62c4e9685d0db54aade092'/>
<id>urn:sha1:df97bcaea2d6c24ddd62c4e9685d0db54aade092</id>
<content type='text'>
This reverts commit 8a3999bc708e8468ff79665e3cbdfccd603160e1.

I realized that this should go in a major release at least, because it
has the potential to break scripts that rely on the old behavior of
ignoring $srctree for the filename passed to Kconfig.__init__().

A dummy release will bump the version to 9.4.2. Any future release with
the change will be 10.0.0.
</content>
</entry>
<entry>
<title>rsource documentation nits</title>
<updated>2018-08-17T20:21:59Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-17T20:21:59Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=3c5ae3f36cf626e79f281b80706b617b76f57060'/>
<id>urn:sha1:3c5ae3f36cf626e79f281b80706b617b76f57060</id>
<content type='text'>
Fix some grammar nits, and add a motivation at the end (wanting to
create self-contained Kconfig trees that can appear anywhere relative to
the top-level Kconfig file).
</content>
</entry>
<entry>
<title>Fix $srctree logic for the top-level Kconfig file</title>
<updated>2018-08-17T19:35:42Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-17T19:04:43Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=8a3999bc708e8468ff79665e3cbdfccd603160e1'/>
<id>urn:sha1:8a3999bc708e8468ff79665e3cbdfccd603160e1</id>
<content type='text'>
Due to a major design braino, the top-level Kconfig file passed to
Kconfig.__init__() wasn't looked up relative to $srctree, breaking
out-of-tree usage for e.g. menuconfig.

With this change, Kconfig files are consistently looked up relative to
$srctree, which makes a lot more sense.

Also remove note re. loading a subset of Kconfig files. Saying that the
top-level file and all source'd Kconfig files are looked up relative to
$srctree should make the behavior clear enough.
</content>
</entry>
<entry>
<title>Use += instead of extend()</title>
<updated>2018-08-14T08:29:24Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-14T08:00:53Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=b7be018fba77db3a9ff11faf980c600d4bbb2fa8'/>
<id>urn:sha1:b7be018fba77db3a9ff11faf980c600d4bbb2fa8</id>
<content type='text'>
+= also does an in-place modification for lists, and it's a bit faster.

Also get rid of an 'if node.defaults' tests. Both symbols and choices
can have defaults, and it's not worthwhile as an optimization either.
</content>
</entry>
<entry>
<title>Simplify menuconfig-without-prompt warning</title>
<updated>2018-08-12T06:22:46Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-12T06:22:46Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=43480de6b2e50dc424232e9b9c97b19502f3e354'/>
<id>urn:sha1:43480de6b2e50dc424232e9b9c97b19502f3e354</id>
<content type='text'>
node.item is already available as 'sym'.
</content>
</entry>
<entry>
<title>Simplify _warn_select_unsatisfied_deps() a bit</title>
<updated>2018-08-12T05:25:17Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2018-08-12T05:25:17Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=40d45c0284838ce4df3ae8d36a867fa0d754e3a3'/>
<id>urn:sha1:40d45c0284838ce4df3ae8d36a867fa0d754e3a3</id>
<content type='text'>
select_val was only used in a single place, and there's no real harm in
calculating expr_value(self.direct_dep) twice for a warning.
</content>
</entry>
<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>
</feed>
