> > What about, that this is the first ever prompt, that must be shown and > written to the .config? Two issues to fix before we can do this: 1) chocie values cannot have more than one prompt 2) We need to share much more Kconfig* between the individual architectures First step is to let all arch's use drivers/Kconfig
Let's get the two items above solved then we can revisit adding arch selection to kconfig (where it belongs in the end). And neither require a rewrite of kconfig... > Also, i'd like to propose sequencing of config-enable-build-this-unit > in config file(s), thus Makefile(s) (sometimes very small and stupid) > will be not necessary. Additional link ordering can be supplied as > meta-config information there. Shell scripting, very ugly in the view > of make syntax, will be natural in config files. Extending build > process to get hidden dependencies or right linking/other magic is > part of particular configuration. Hm? Discussed before but so far no patches has shown up. Sam ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel