Bug Report: Regression in Cygwin 2.11.0-1

[Andrey Repin]

Greetings, David Allsopp!

>> In terms of this OCAML build system problem:
>> 
>> Please fix your build system.  Do not mix POSIX and Win32 paths, use POSIX
>> paths only.  Backslashes are *no* drop-in replacement for slashes.

> The "problem" for us is more subtle than this. The program which is
> generating that path is not a Cygwin executable, so it is correctly
> combining a path it has been supplied (the ../stdlib which has been supplied
> via Cygwin's make) with a filename, so it uses a backslash. It's been on my
> TODO for years to enhance to understand that the program it's supplying the
> path back to is a Cygwin executable and so sort it out properly but, well,
> we're a small number of maintainers! That said, WSL is forcing us to address it properly...

You CAN just send back forward slashes. Windows don't care.
If any program would choke, it would be that program's problem after all.


-- 
With best regards,
Andrey Repin
Sunday, September 2, 2018 0:51:18

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple