Hello Wolfgang.
> U-Boot is very flexible to configure, and as is it is not trvial to > tell if a specific piece of code actually gets linked into the final > product. I wonder if we should turn the comment as we have it now > into actual code, i. e. into a preprocessor macro that compiles the > license ID into the generated object file (probably into a separate > section so you can decide whether or not you want to include this > ieven into the final binary image). Interesting! Linux Kernel has MODULE_LICENSE macro for device drivers, for example: MODULE_LICENSE("Dual BSD/GPL"); MODULE_LICENSE("GPL"); License information is embedded into *.ko file. Similar idea? I want the preprocessor macro placed on the top of each file, if it is used in substituion for SPDX Lincense Identifier. This idea seems to fit only to C sources. We should use different approach depending on the type of files. Right? macro approach: C source file comment block: makefile, python scripts, shell scripts... Best Regards Masahiro Yamada _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot