This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: 3.81 and windows paths


> There is no advantage using cygwin if you want to use a Makefile which
contains
> MS-DOS paths.  Using MinGW makes perfect sense in that case.

I strongly disagree with this statement.  A primary benefit of using Cygwin
is that so many Linux-like tools are available from one central installer.
If you have a Makefile system that uses Cygwin for more than just the make
binary and binutils (aka more than what MinGW provides), it becomes
irritating to developers that they need to install at least two software
products (Cygwin and MinGW in this case) and create special path voodoo just
for one product.

I can imagine that the immediate response to this complaint will be "fix
your Makefiles to work with Cygwin if it's such an important component."  As
others have mentioned, this is no simple task in very large Makefile systems
that support a wide variety of compilation toolchains.  Cygwin make has
supported Win32 paths for a long time, so much that I would say that people
have come to rely on it.  I am not saying that the changes are impossible;
just that it is a larger inconvenience than some may realize.

William Sheehan
Builds Engineer / Network Administrator
Open Interface North America



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]