Searched hist:"9 a926d4354d84e424e738a6d401328340400331b" (Results 1 – 3 of 3) sorted by relevance
/linux/scripts/kconfig/ |
H A D | gconf.c | diff 9a926d4354d84e424e738a6d401328340400331b Sat Oct 20 01:06:25 CEST 2012 Yann E. MORIN <yann.morin.1998@free.fr> kconfig: get CONFIG_ prefix from the environment
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 hard-coded value if not found.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Michal Marek <mmarek@suse.cz>
|
H A D | nconf.c | diff 9a926d4354d84e424e738a6d401328340400331b Sat Oct 20 01:06:25 CEST 2012 Yann E. MORIN <yann.morin.1998@free.fr> kconfig: get CONFIG_ prefix from the environment
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 hard-coded value if not found.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Michal Marek <mmarek@suse.cz>
|
H A D | lkc.h | diff 9a926d4354d84e424e738a6d401328340400331b Sat Oct 20 01:06:25 CEST 2012 Yann E. MORIN <yann.morin.1998@free.fr> kconfig: get CONFIG_ prefix from the environment
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 hard-coded value if not found.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Michal Marek <mmarek@suse.cz>
|