On 2025-08-05 02:44, Old, Oliver via Cygwin wrote:
Hello Andrey,

Then do not mix environments.

That is not my choice, but rather my supervisor's choice. I began
engineering our new CMake-based build system purely with MinGW
toolchains in mind, statically linked ones even since I already know how
well-received it would be if I required people to install a MinGW
environment and had them add it to their PATH.

Then I was told we might have to abandon this new system if we can't
keep using our Cygwin toolchains.

I know it is very unwise to attempt this and entirely unproductive.

Cygwin with automation scripts.

I wish that was good enough, but I'm supposed to make it work with all
the GUI and integrated debugging capabilities the other toolchains have.
It is so very frustrating.

Back to the technical aspects: I just don't see why the current command
line handling is supposed to be good. I find it to be very surprising as
its entire purpose is interfacing with non-Cygwin software. Why should

NO - its entire purpose is interfacing with Cygwin and other POSIX sosftware, including on other systems, from MS cmd if users insist, but according to POSIX rules! We now have only limited support for some non-POSIX text files.

the "non-Cygwin" software assume the command line to be parsed according
to Bash's rules?

It allows us to use tools based on POSIX standards, like terminals, shells, and utilities, under Windows, without running under a VM like WSL or alternatives, and with access to Windows filesystems, without *each* of us having to buy pieces of software which would work together,(Borland, 386^Max), or find and install a working toolchain, and build *each* GNU or BSD utility from sources *ourselves* (like news:comp.sources.…), as we used to have to do.

        https://cygwin.com/faq.html

        https://cygwin.com/:

"Get that Linux feeling - on Windows

"What...

...is it?

"Cygwin is:

• a large collection of GNU and Open Source tools which provide functionality similar to a Linux distribution on Windows.
• a DLL (cygwin1.dll) which provides substantial POSIX API functionality.

...isn't it?

"Cygwin is not:

• a way to run native Linux apps on Windows. You must rebuild your application from source if you want it to run on Windows. • a way to magically make native Windows apps aware of UNIX® functionality like signals, ptys, etc. Again, you need to build your apps from source if you want to take advantage of Cygwin functionality."

--
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                -- Antoine de Saint-Exupéry

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

Reply via email to