X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17610.8103.778129.918123@lemming.engeast.baynetworks.com> Date: Fri, 28 Jul 2006 10:31:03 -0400 To: "John W. Eaton" Cc: bug-make@gnu.org, cygwin@cygwin.com Subject: Re: 3.81 and windows paths In-Reply-To: <17610.7126.60597.468701@segfault.lan> References: <20060727195042.GC27890@brasko.net> <44C92033.A2978A8E@dessent.net> <17609.11132.462789.443104@lemming.engeast.baynetworks.com> <20060727221136.GD6653@trixie.casa.cgf.cx> <17610.6020.12729.506044@lemming.engeast.baynetworks.com> <17610.7126.60597.468701@segfault.lan> 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 %% "John W. Eaton" writes: jwe> On 28-Jul-2006, Paul D. Smith wrote: | Regardless, I still wonder whether my idea of building make for a POSIX | environment with Cygwin, but setting HAVE_DOS_PATHS explicitly, would | work. jwe> If this could cause some valid Makefiles to do the wrong thing as jwe> cgf suggests might happen, Hm. I don't think I saw that message? Certainly there are obscure cases where enabling DOS path support will behave differently, but they're pretty rare I believe. Is this a Cygwin thing? jwe> then can we at least make the behavior optional, perhaps with a jwe> command line option or magic target (maybe jwe> ".WINDOWS_FILENAMES:")? This would be very tricky: right now all the code to do DOS vs. POSIX pathnames is controlled through #ifdefs, so it's a compile-time thing. Changing it to a runtime thing would be a lot of work, I think... the #ifdeffing in GNU make is kind of a mess, with all the different ports we support. Honestly, I don't see a lot of benefit to it. On a Windows system, even in Cygwin, I would assume that everyone would always expect anything that looked like a Windows pathname to be treated like a Windows pathname. We're not talking about enabling this support on UNIX, just in Cygwin. -- ------------------------------------------------------------------------------- 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/