On Fri, Dec 13, 2013, Corinna Vinschen wrote:
> On Dec 13 10:06, Adrien Nader wrote:
> > There are two issues here:
> > - symlink fallback on windows
> > - Windows XP and symlink fallback
> > 
> > tl;dr: don't mind the warnings, they're harmless; Windows XP support is
> > an issue (but at least read the last paragraph)
> > 
> > Full explanation below.
> > 
> > Since the package is a *native* windows executable, it cannot do POSIX
> > symlinks. Win32 symlinks are slightly different and also have several
> > issues which make them not usable.
> > 
> > The approach to provide something equivalent to how symlinks are used
> > inside packages is:
> > - build on linux
> 
> - or Cygwin.  It supports its own symlinks which work on XP as well.

Yes but they would require other tools to also be cygwin executables.

The symlink emulation stuff is not meant for crazy things. Packages
mostly have a simple uses for symlinks and these uses can be emulated
through with hardlinks and junctions.
No attempt is done to handle fancy uses or exact (or close) posix
conformance. If that is what is wanted, cygwin is of course the right
tool to use.

-- 
Adrien Nader

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to