On Wed, 27 Mar 2002 16:22:46 +1100, Brendan J Simon <[EMAIL PROTECTED]> wrote: >The CM system (Aegis) uses symbolic links to implement branches. eg. >project.2.5.3.6 has four branches from the root of the repository. If I >am working in the last branch then files in the that branch are sym >links to the previous branch which are symlinks to the previous branch >which are symlinks to the previous branch .............. until a real >file is reached. eg. if there is a file in the root called foo.c then >all deeper branches contain a symlink of foo.c to the previous branch. > If project.2.5 requires a slightly different version of foo.c, then the >file can be checked out and edited and checked in for that branch. Now >all foo.c files below project.2.5 will be symlinks to the new file and >all branches between the root and project.2.5 will be linked to the old >file. > >My question is, does kbuild ignore the symlinks and keep searching (via >VPATH I assume) the path defined with KBUILD_SRCTREE_XXX ?? ie. will it >eventuall find the real file if I setup the environment varialbes >properly all will it just barf at the first symlink it finds ?
Current kbuild 2.5 does not support any symlinks at all in the source tree. When I get around to solving the problems with symlinks and timestamps, Aegis should be OK, but not right now. _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
