Keith Owens wrote:
>On Mon, 25 Mar 2002 13:45:04 +1100,
>Brendan J Simon <[EMAIL PROTECTED]> wrote:
>
>>Does kbuild-2.5 work with symbolic links ?
>>
>
>Not at the moment. The tree walk code must not follow symlinks to
>directories, othereise it gets very confused about where all the input
>files are. So the tree walk code uses lstat instead of stat, but lstat
>is no good for plain files because it gets the timestamp of the symlink
>instead of the real file. Until I can correct the tree walk code and
>convince myself that symlinks will not cause other problems, kbuild 2.5
>does not support symlinks. Maybe later.
>
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 ?
Thanks,
Brendan Simon.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
