X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: make 3.81-1 vs. 3.80-1 and C:\... style dependency handling differences Date: Wed, 9 Aug 2006 17:55:09 +0100 Message-ID: <007001c6bbd4$92841b70$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 09 August 2006 17:26, Buster wrote: >> It seems that http://cygwin.com/cygwin-ug-net/ov-ex-win.html needs to >> be amended because it says (copy of the last sentance)... >> >> All tools may be used from the Microsoft command prompt, with >> full support for normal Windows pathnames. > > I don't think so. The previous sentences restrict that 'all' to the > "set of tools capable of writing console or GUI executables that rely > on the Microsoft Win32 API", that is, the mingw32 compilers, linker, > and so on. No, it does need to be clarified. What it means is that all tools will accept windows pathnames *AT THE COMMAND LINE PROMPT* - because the cygwin dll will do all the necessary translation on argv - but it does not mean that all tools will accept windows pathnames in their config files, scripts, or any other input that only the tool in question knows anything about so the dll can't help. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/