X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17610.6020.12729.506044@lemming.engeast.baynetworks.com> Date: Fri, 28 Jul 2006 09:56:20 -0400 To: bug-make@gnu.org, cygwin@cygwin.com Subject: Re: 3.81 and windows paths In-Reply-To: <20060727221136.GD6653@trixie.casa.cgf.cx> References: <20060727195042.GC27890@brasko.net> <44C92033.A2978A8E@dessent.net> <17609.11132.462789.443104@lemming.engeast.baynetworks.com> <20060727221136.GD6653@trixie.casa.cgf.cx> X-Mailer: VM 7.19 under Emacs 21.4.1 From: "Paul D. Smith" Reply-To: "Paul D. Smith" Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com %% Christopher Faylor writes: cf> There is no advantage using cygwin if you want to use a Makefile cf> which contains MS-DOS paths. Using MinGW makes perfect sense in cf> that case. Despite having suggested this repeatedly, it seems cf> some users are still not clear on this concept. Well, I can understand the desire to use a generally POSIX environment, but still have some requirements that it interact with native Windows in some ways. I did read the thread on the cygwin mailing list so I know people could work around it with macros or cygpath or whatever. cf> If you want to use a Makefile which works in a Cygwin environment, cf> however, then obviously you need to build it with a Cygwin gcc. You'll have to forgive my virtually complete ignorance of all things Windows, even Cygwin, but if you have a minute... why? I mean, if there is no special Cygwin code in make any longer, then can't people use a native Windows build of make and have it invoke tools in the Cygwin environment? Or is there something special going on that means this won't work? Regardless, I still wonder whether my idea of building make for a POSIX environment with Cygwin, but setting HAVE_DOS_PATHS explicitly, would work. cf> Again, I'm sorry for any confusion this may have caused. Absolutely no problem Christopher; I hope I didn't sound peeved because I'm not. I'm happy to see this change, and I'm happy that I understand the source of the confusion some Cygwin users have been having lately. It's all good! Cheers! -- ------------------------------------------------------------------------------- Paul D. Smith Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist -- 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/