On Thu, Jul 27, 2006 at 03:40:18PM -0700, Brian Dessent wrote: >William Sheehan wrote: >>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. > >In that case, spend your time working with the Make developers to get a >patch accepted upstream that enables Windows path handling in Cygwin >builds, so that there is not a large and cumbersome out-of-tree patch >that has to be ported to each new make release. Remember this is a >volunteer effort, and SHTDI. Or you can stick with make 3.80.
Actually, we have had people who have complained because make became confused by certain uses of a ':' in the old version of make. I see now that this is because of the attempt to interpret a valid make rule as a MS-DOS path. So, I'm less inclined to want to recommend an upstream patch. I don't think I want to break valid makefiles which work on linux. cgf -- 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/