[Omake] Re: vmount via hard links on Win32

[David Kågedal]

David Kågedal <davidk at lysator.liu.se> writes:

> "Dmitry Bely" <dmitry.bely at gmail.com> writes:
>
>> On 9/14/06, David Kågedal <davidk at lysator.liu.se> wrote:
>>
>>> > The following patch works for me. Somewhat like a hack (those NTFS
>>> > hard links have strange behaviour), but still does the job. Can
>>> > something like that be included into the distribution?
>>>
>>> I'm just curious, why do you need to link (or copy) the files at all?
>>
>> You mean why I am using omake's vmount? Because I like to build debug
>> and release versions simultaneously. Why link is better than copy?
>> Because the error message points to the file inside vmounted dir
>> (release or debug). In the case of copy I cannot jump to the error
>> message and edit the file - any changes will be lost.
>
> No, I mean why do you need to link or copy files while you are using
> vmount.  The whole point of vmount is that it can find the source
> files in their original locations, just so you *don't* have to copy
> nor link them.
>
> Just use vmount without any flags.  It works fine, as long as you
> apply the patch I posted for compiling C (Svn has been updated with
> it, plus mor of similar fixes, thank you!).  I haven't tried any
> O'Caml stuff, but I don't why it should work equally well there.

Two words missing there:  "I don't see why it should not work equally well"

-- 
David Kågedal