[Kconfig] 是不是放弃“option env=”了？

[sp-cai]

[Kconfig] 是不是放弃“option env=”了？

[BernardXiong]

需要首先验证的是，如果放弃option env=的方式，studio是否没问题。如果没问题，那么就可以考虑放弃了。当然也有一种方式是修改kconfiglib的代码，但这个是否会涉及到上游代码了。

[sp-cai]

需要首先验证的是，如果放弃option env=的方式，studio是否没问题。如果没问题，那么就可以考虑放弃了。当然也有一种方式是修改kconfiglib的代码，但这个是否会涉及到上游代码了。

上游有他的考量，想在上游加上恐怕很难指望了。如果还有用，也可以考虑在其它地方扩展。
以下是来自上游(Kconfiglib)可能与之相关的信息以供参考：

• Environment variables are expanded directly in e.g. source and mainmenu statements, meaning option env symbols are redundant.

  This is the standard behavior with the new Kconfig preprocessor,which Kconfiglib implements.

  option env symbols are accepted but ignored, which leads the caveat that they must have the same name as the environment variables they reference (Kconfiglib warns if the names differ). This keeps Kconfiglib compatible with older Linux kernels, where the name of the option env symbol always matched the environment variable. Compatibility with older Linux kernels is the main reason option env is still supported.

  The C tools have dropped support for option env.

文中意思似乎是已经放弃支持option env了，转而推新的 Kconfig 预处理标准，如：

BSP_DIR := ../../..
source "$(RTT_DIR)/Kconfig"

[BernardXiong]

需要首先验证的是，如果放弃option env=的方式，studio是否没问题。如果没问题，那么就可以考虑放弃了。当然也有一种方式是修改kconfiglib的代码，但这个是否会涉及到上游代码了。

上游有他的考量，想在上游加上恐怕很难指望了。如果还有用，也可以考虑在其它地方扩展。 以下是来自上游(Kconfiglib)可能与之相关的信息以供参考：

• Environment variables are expanded directly in e.g. source and mainmenu statements, meaning option env symbols are redundant.
  This is the standard behavior with the new Kconfig preprocessor,which Kconfiglib implements.
  option env symbols are accepted but ignored, which leads the caveat that they must have the same name as the environment variables they reference (Kconfiglib warns if the names differ). This keeps Kconfiglib compatible with older Linux kernels, where the name of the option env symbol always matched the environment variable. Compatibility with older Linux kernels is the main reason option env is still supported.
  The C tools have dropped support for option env.

文中意思似乎是已经放弃支持option env了，转而推新的 Kconfig 预处理标准，如：

BSP_DIR := ../../..
source "$(RTT_DIR)/Kconfig"

那就需要验证studio中的web kconfig是否支持这样的方式了。