[coreboot] kbuild troubles

Stefan Reinauer stepan at coresystems.de
Sun Oct 11 12:54:41 CEST 2009


Peter Stuge schrieb:
> Rudolf Marek wrote:
>   
>> config.h
>> define CONFIG_EPIA_VT8237R_INIT 0
>>     
> ..
>
>   
>> But a code:
>>
>> southbridge/via/vt8237r/vt8237r_lpc.c:#ifdef CONFIG_EPIA_VT8237R_INIT
>>
>>
>> Which means it gets COMPILED IN
>>     
>
> --8<-- util/kconfig/confdata.c:714 conf_write_autoconf()
>         for_all_symbols(i, sym) {
> ..
>                 switch (sym->type) {
>                 case S_BOOLEAN:
>                 case S_TRISTATE:
>                         switch (sym_get_tristate_value(sym)) {
>                         case no:
>                                 fprintf(out, "CONFIG_%s=n\n", sym->name);
>                                 fprintf(out_h, "#define CONFIG_%s 0\n", sym->name);
>                                 break;
>                         case mod:
>                                 fprintf(out, "CONFIG_%s=m\n", sym->name);
>                                 fprintf(out_h, "#define CONFIG_%s_MODULE 1\n", sym->name);
>                                 break;
>                         case yes:
>                                 fprintf(out, "CONFIG_%s=y\n", sym->name);
>                                 fprintf(out_h, "#define CONFIG_%s 1\n", sym->name);
>                                 break;
> -->8--
>
> Do we change confdata.c to not include unset booleans - or do we
> change every #ifdef to #if ? I like the latter.
>   
If we change all the #ifs code we should revert to the original Kconfig 
behavior.

Stefan




More information about the coreboot mailing list