b37bcf2fc0
When a configuration file fragment ends in a line that is not terminated by a \n, it will mange the pasting of the following fragment. For example, in file1.prj: CONFIG_SETTING_A=34 CONFIG_SETTING_B=12 and file2.prj: CONFIG_SETTING_C=56 would become: CONFIG_SETTING_A=34 CONFIG_SETTING_B=12CONFIG_SETTING_C=56 because there was no \n at the end of CONFIG_SETTING_B=12. This makes the kconfig parser to reject CONFIG_SETTING_B and to loose CONFIG_SETTING_C, which then has random consequences. So, to avoid that problem, always add a newline after a config fragment. Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com> |
||
|---|---|---|
| .. | ||
| lxdialog | ||
| check.sh | ||
| checkconfig.py | ||
| conf.c | ||
| confdata.c | ||
| config | ||
| diffconfig | ||
| expr.c | ||
| expr.h | ||
| gconf.c | ||
| gconf.glade | ||
| images.c | ||
| kxgettext.c | ||
| list.h | ||
| lkc_proto.h | ||
| lkc.h | ||
| Makefile | ||
| mconf.c | ||
| menu.c | ||
| merge_config.sh | ||
| nconf.c | ||
| nconf.gui.c | ||
| nconf.h | ||
| POTFILES.in | ||
| qconf.cc | ||
| qconf.h | ||
| streamline_config.pl | ||
| symbol.c | ||
| util.c | ||
| zconf.gperf | ||
| zconf.hash.c_shipped | ||
| zconf.l | ||
| zconf.lex.c_shipped | ||
| zconf.tab.c_shipped | ||
| zconf.y | ||