[Omake] Re: vmount problems

[Dmitry Bely]

On 8/30/06, David Kågedal <davidk at lysator.liu.se> wrote:

> >>> 2. Mention that scanner rules necessitate the -l flag to vmount.
> >>
> >> On Win32 I need both the -l and the undocumented -f flag (OMake 0.9.6).
> >> Otherwise some files will be missing, for example headerfiles with no
> >> corresponding .c file.
> >
> > Here i disagree strongly, OMake should not invent workarounds for
> > ocaml(dep|c|opt)s shortcommings. Linking/copying the files is just
> > wrong, in emacs you end up visiting wrong files, and in case of
> > copying, on Win32, modify them, mayhem will shortly follow.
>
> Not to mention that you use twice the amount of disk space.  Having to
> copy or even symlink source files to the build directory is a really
> bad idea.
>
> >From reading through the mail archives and looking at
> http://bugzilla.metaprl.org/show_bug.cgi?id=557 it appears that it's
> impossible to use vmount without having to copy files to the build
> tree (I count symlinks as copies, as I want something that works
> equally well on windows).  Why is this so, given that make has the
> very similar vpath feature that doesn't require it?

Why not to use hardlinks on Win32 for vmount? Just thinking of the
patch that will do just that.

- Dmitry Bely