Hello Michael, On Sun, 13 Mar 2011 13:17:40 +0100, Michael Olbrich wrote: >> I didn't want to put all the content from >> /usr/local/lib/ptxdist-2011.02.0/config/Kconfig into my own config. > > Actually imho config/Kconfig is mostly a template to be copied. I do this > for all projects. Maybe we can move stuff elsewhere, so it will change less > often?
I had a little time now to investigate this further, but I have to admit I have no idea for an elegant solution. > Lets see: >> # >> # config/Kconfig: Main menu structure definition >> # Copyright (C) 2002-2006, 2009 by Robert Schwebel >> <r.schwe...@pengutronix.de> >> # >> >> mainmenu "PTXdist $CONFIGFILE_VERSION" >> >> config MODULES >> bool >> default y > > Hmm, it really doesn't matter where we put this. rules/Kconfig maybe? > However moving this may result in warnings for existing projects. This mainmenu entry is the problem. If you want it for projects which do not extend the menu, it hast to be in config/Kconfig I guess. It disturbes, if you extend the menu as suggested in the application note as I did. You could drop it completely as in previous versions of ptxdist of course. ;-) What I did now is what I mentioned before: Commenting out the mainmenu line in /usr/local/lib/ptxdist-*/config/Kconfig and put it into my own Kconfig which is just the template from rules/templates/kconfig/Kconfig with some additional lines adding my own menu entries. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- ptxdist mailing list ptxdist@pengutronix.de
