Michael Elizabeth Chastain <[EMAIL PROTECTED]>:
> My ideas for a roadmap:
>
> . pick one patch to go first rather than put both in the same point
> release.
I think that might reduce the coordination problems, yes.
> . i favor doing cml2 first, because kaos makefiles depend on the cml.
I didn't have an opinion about this until Keith's description gave me
a headache. Now I think I would like CML2 to go in first and let him
handle the makefile interface.
> . 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.
Depends on how you interpret "supports". Fundamentally CML2 doesn't
care where the input and output lives. Input and output locations are
specifiable on the command line with defaults to the current
directory.
> . 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.
Why do this inside CML2 rather than by macroexpansion in the makefile command?
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
See, when the GOVERNMENT spends money, it creates jobs; whereas when the money
is left in the hands of TAXPAYERS, God only knows what they do with it. Bake
it into pies, probably. Anything to avoid creating jobs.
-- Dave Barry
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
