> infact yes if the project name could be configurable it will avoid to modify > it and we could use it as is > > I've notice 3 names > > kernel, > Kernel, > Linux Kernel > > if instead of hard coding it we could use a symbol to configure it it will > make it integrable as is > > one other think it will be good to avoid KERNEL something in the env or the > default symbol and use a more generic one as for KERNELVERSION use > RELEASEVERSION as example The solution I have in mind is to try to add the relevant information to the Kconfig files. Today the title is hardcoded in the frontends (menuconfig, nconfig etc). We could instead pick this up from the mainmenu entry. So we in a Kconfig file could have: mainmenu "My application configuration - version $VERSION" config VERSION string option env=VERSION The text in mainmenu will have all references to $SOMETHING expanded to the string representation of that symbol. And we can use existing functionality to pick up environment variables. The frontends needs to be adapted as well as the kconfig backend. But doing the above I guess we have 'fixed' almost all kernel references. Sam _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
