I have been using NTFS symlinks sparingly without Ill effect.
Usually they are set up via a special interactive CMD.exe session, sometimes
through the MSYS (=MSYSTEM) shell run as administrator (windows 7, 65b
system).
So I built a new test library in system I have on the D: drive and sent it
to /usr/local32 as install location. Then I used it after making an NTFS
symlink in
C:\usr as such:
ln -s /d/mingw/msys32/usr/local32 /c/usr/local32d
So far so good - my new library for testing is over in "local32" and I test
it
by compiling & linking a program, then I (am in MSYSTEM=MINGW32 MSYS=""
shell at this point) want to list the synmlinked directory and I copy
a command down from my history which is wrong, I reissued
ln -s /d/mingw/msys32/usr/local32 /c/usr/local32d
And the result is about 20 iterations of
local32:
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
bin/ lib/ share/ local32/
etc.
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
