Re: [patch 11/18] kconfig CROSS_COMPILE option

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > > Another approach would be to ask kbuild for
> > > this information so we do not expose various filenames to the
> > > outer world.
> > 
> > For shell scripts and makefiles, running a command like make and retrieving
> > its output via pipe is de rigueur.  But for some other programs it might be
> > substantially less hassle to just read plain files.  That's what I was
> > thinking, anyway.  (I only really think that $ARCH is something that anyone
> > would want to fetch before they'd run make anyway, and I guess $SUBARCH in
> > the case of ARCH=um, but not $CROSS_COMPILE.)
> > 
> > > This is analogous to the way we ask for
> > > kernelrelease and kernelversion these days.
> > 
> > Except that include/config/kernel.release is there for all to see (when
> > referring to /lib/modules/.../build directory, e.g.), so perhaps some
> > people are in fact using that.
> 
> So when I move that file to include/generated I will break users script silently - sigh.
> 
> Revised patch following your guidelines below.
> Does this look better to you?

Well.. having that option in .config, so it can be easily transported
between trees (as proposed originally) would be even nicer, but I
guess this is better than nothing.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html