On Mon, 25 Jun 2001 07:35:05 -0700,
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
>Actually I think of myself as more "emeritus" than "honcho".
>
>My ideas for a roadmap:
>
>. pick one patch to go first rather than put both in the same point
> release.
I was thinking of kbuild 2.5 with support for both CML1 and CML2, at
least to start off with. Then drop CML1.
>. i favor doing cml2 first, because kaos makefiles depend on the cml.
Only a little. I need a valid .config, I do not care how it is built.
It could be CML1, CML2 or AC's version of CML1, it does not matter to
the bulk of my code how .config is built. scripts/Makefile-2.5 has to
support CML but that is relatively trivial.
>. kaos makefiles have separate source and target trees. it looks like
> cml2 does not have support for separate source and target: the output
> file goes into the current directory, and the source files come from a
> "find ." command.
>
>. i think cml2 needs to honor keith's environment variables, KBUILD_SRCTREE
> and KBUILD_OBJTREE, plus the "forest" stuff. If the variables are
> not there, default to current directory, so that cml2 works with the
> old Makefiles during the transition period.
No need for any CML code to know about separate directories. CML1 does
not know about separate source and object either, I fool it by building
the symlink forest. At a quick glance, I can handle CML2 exactly the
same way. IOW, we should not need any code changes for CMLx when
moving from from 2.4 to 2.5.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
