On Mon, Oct 08, 2007 at 10:02:55PM +0200, Sam Ravnborg wrote: > One of the complaints that I continue to hear is that kbuild > is lacking a way to 'remember' the ARCH and CROSS_COMPILE > values originally used.
Yea, finally. What about, that this is the first ever prompt, that must be shown and written to the .config? The zeroth one is an config entry of kernel version(s), .config can configure and thus build successfully. This are among other ideas about kconfig/kbuild, you know nothing about yet. So, what do you think? 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? And i want to repeat this to the wall: make is stupid `test -nt` (non POSIX, but accepted my shells and GNU test feature). Making any kind of hashing to make dream of kbuild-2.5 developers/fans -- more complete `up-to-date' heuristic possible, is just like `md5sum > $OBJDIR/heuristic.com`, which is config selectable (for those, who don't like a bit of slowdown). -- -o--=O`C #oo'L O <___=E M ------------------------------------------------------------------------- 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
