On Fri, 28 Jun 2002 00:14:52 +0200,
Sam Ravnborg <firstname.lastname@example.org> wrote:
>In order to prepare for separate obj and src trees make use of $objtree
>within scripts/Menuconfig and scripts/Configure.
>All temporary and all result files are located in directory pointed at
>This functionality is foreseen useful for both current kbuild and kbuild-2.5
Wrong approach. This messes up kbuild 2.5. The config tools should
not know where the files are being read from or written to, you have
hard coded knowledge about the tree structure into the config system.
kbuild 2.5 handles this by constructing a set of symlinks then invoking
the configure system under those symlinks, followed by copying any
results to their destination. The symlink tree completely isolates
the config system from any knowledge of where its inpuuts and outputs
really are, everything looks local.
You have a 750+ line patch to imbed tree knowledge into configure, that
knowledge will have to be duplicated for any new CML tools. kbuild 2.5
does it in a few lines of scripts/Makefile-2.5 which automatically
works for any new CML code.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 30 2002 - 22:00:12 EST