Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v10.0.0 2018-08-18T01:15:46Z 2018-08-18T01:15:46Z Ulf Magnusson ulfalizer@gmail.com 2018-08-18T01:15:16Z urn:sha1:f0c615cf0dc18c03fd860e5f466c87bb661c8b6f Adds commit 8a3999b ("Fix $srctree logic for the top-level Kconfig file"), which fixes an old braino: The top-level Kconfig file passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree operation for scripts unless ugly manual $srctree hacks were added. All Kconfig files are now consistently looked up relative to $srctree. This is a backwards-incompatible change (though with a simple fix), so the major version is bumped. A note is printed on errors that might be due to the changed behavior. 2018-08-18T01:15:46Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T19:04:43Z urn:sha1:f247ddf618ad29718e5efd3e69f8baf75d4d347b Due to an old design braino, the top-level Kconfig filename passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree usage for e.g. menuconfig. Fixing it required ugliness like srctree = os.environ.get("srctree", "") kconfiglib.Kconfig(os.path.join(srctree, "Kconfig")) Change the behavior of Kconfig.__init__() to look up the top-level Kconfig file relative to $srctree. This means that all Kconfig files (both the top-level file and any source'd files) now use $srctree, which makes the vast majority of scripts just work when running out-of-tree. Also remove the 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. Print a note about the new behavior whenever the top-level Kconfig file can't be opened, as this change could be breaking for some scripts. This is a slight backwards-compatiblity break, so the major version will be bumped. 2018-08-17T23:37:58Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T23:11:40Z urn:sha1:af7f6c30ece8536a60d69da58d924155789c2918 This just reverts commit 8a3999f ("Fix $srctree logic for the top-level Kconfig file"), so that it can go in a major release instead. I realized it has enough breakage potential for existing scripts to warrant a major version bump. 2018-08-17T23:10:41Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T23:07:23Z urn:sha1:df97bcaea2d6c24ddd62c4e9685d0db54aade092 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. 2018-08-17T20:21:59Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T20:21:59Z urn:sha1:3c5ae3f36cf626e79f281b80706b617b76f57060 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). 2018-08-17T19:42:29Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T19:37:26Z urn:sha1:5d973e81c192b8e214437317eb3834fba93f1f0f - Commit 8a3999b ("Fix $srctree logic for the top-level Kconfig file") fixes a major braino where the top-level Kconfig file passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree operation for e.g. menuconfig. All Kconfig files are now consistently looked up relative to $srctree. - Misc. internal code cleanup 2018-08-17T19:35:42Z Ulf Magnusson ulfalizer@gmail.com 2018-08-17T19:04:43Z urn:sha1:8a3999bc708e8468ff79665e3cbdfccd603160e1 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. 2018-08-14T08:29:24Z Ulf Magnusson ulfalizer@gmail.com 2018-08-14T08:00:53Z urn:sha1:b7be018fba77db3a9ff11faf980c600d4bbb2fa8 += 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. 2018-08-12T06:22:46Z Ulf Magnusson ulfalizer@gmail.com 2018-08-12T06:22:46Z urn:sha1:43480de6b2e50dc424232e9b9c97b19502f3e354 node.item is already available as 'sym'. 2018-08-12T05:25:17Z Ulf Magnusson ulfalizer@gmail.com 2018-08-12T05:25:17Z urn:sha1:40d45c0284838ce4df3ae8d36a867fa0d754e3a3 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.