On Mon, Oct 08, 2007 at 11:12:56PM +0200, Adrian Bunk wrote:
On Mon, Oct 08, 2007 at 10:02:55PM +0200, Sam Ravnborg wrote:
...
The settings are stored in the build directory in a file
named Kbuild.config (should it be a .dot file?).
...
A .dot file sounds better.
I will make it .kbuild.
On Tue, Oct 09, 2007 at 06:17:43AM +0200, Sam Ravnborg wrote:
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
what occupying all my time now is to try
On Tue, Oct 09, 2007 at 08:03:33AM +0200, Sam Ravnborg wrote:
On Mon, Oct 08, 2007 at 11:12:56PM +0200, Adrian Bunk wrote:
...
BTW: I'm currently trying without success to understand why the
drivers/infiniband/{hw/amso1100,ulp/srp}/Kbuild files are not
named Makefile.
Giacomo
On Tue, Oct 09, 2007 at 10:09:06AM -0400, Jeff Dike wrote:
On Tue, Oct 09, 2007 at 12:00:30PM +0200, Sam Ravnborg wrote:
If it is OK to drop the $(SUBARCH) assingment like this then yes.
ARCH?=
CROSS_COMPILE ?=
Does the UML build still work when you do that?
The
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
On Mon, Oct 08, 2007 at 10:02:55PM +0200, Sam Ravnborg wrote:
...
The settings are stored in the build directory in a file
named Kbuild.config (should it be a .dot file?).
...
A .dot file sounds better.
And even if not, generated files should IMHO not share the Kbuild*
namespace with
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
2) We need to share much more Kconfig* between the individual architectures
First step is to let all arch's use drivers/Kconfig
2) isn't terribly difficult, just takes some time and willingness
of $arch maintainers to some changes, but please explain a bit more
why it is needed...?
A
