Keith Owens wrote:
>
> On Fri, 04 Jan 2002 16:42:02 +0100,
> "Giacomo A. Catenazzi" <[EMAIL PROTECTED]> wrote:
> >I have some problem with the KBUILD_SRCTREE, and
> >reading the kbuild-2.5 makefile and the CML2, I
> >think I'm not alone.
>
> What problem are you trying to solve? I don't like solutions without
> knowing what the problem is, it makes it difficult to tell if the
> solution is correct or not.
To give the multiple sources tree to gcc you use a for(i=0,i<=999,i++).
I don't like it, and I don't like that all the tools that need multiple
kernel files sould try the loop.
My proposal is to symplify the source path handled by applications.
And the need of a simplification is obvious. Actual code is so
complex that you hard code the SRCTREE_000 in your Makefile,
instead of parsing the right source.
Also CML2 should use the rules.cml from the various SRCTREE.
And it seems to me not clean to make a loop to search all
available sources also in python.
giacomo
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
