[PATCH 3/3] kconfig: get CONFIG_ prefix from the environment

2012-10-19 Thread Yann E. MORIN
Currently, the CONFIG_ prefix is hard-coded in the kconfig frontends executables. This means that two projects that use kconfig with different prefixes can not share the same kconfig frontends. Instead of hard-coding the prefix in the frontends, get it from the environment, and revert back to

[PATCH 3/3] kconfig: get CONFIG_ prefix from the environment

2012-10-19 Thread Yann E. MORIN
Currently, the CONFIG_ prefix is hard-coded in the kconfig frontends executables. This means that two projects that use kconfig with different prefixes can not share the same kconfig frontends. Instead of hard-coding the prefix in the frontends, get it from the environment, and revert back to

[PATCH 3/3] kconfig: get CONFIG_ prefix from the environment

2012-10-18 Thread Yann E. MORIN
Currently, the CONFIG_ prefix is hard-coded in the kconfig frontends executables. This means that two projects that use kconfig with different prefixes can not share the same kconfig frontends. Instead of hard-coding the prefix in the frontends, get it from the environment, and revert back to

[PATCH 3/3] kconfig: get CONFIG_ prefix from the environment

2012-10-18 Thread Yann E. MORIN
Currently, the CONFIG_ prefix is hard-coded in the kconfig frontends executables. This means that two projects that use kconfig with different prefixes can not share the same kconfig frontends. Instead of hard-coding the prefix in the frontends, get it from the environment, and revert back to