X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B5A1E48.6060803@etr-usa.com> Date: Fri, 22 Jan 2010 14:53:12 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Design issue with new MS-DOS style path warning? References: <81D39E818991E549B1F66EB6A7D18422BE8626@AVSMOEXCL02.activision.com> <4B57DF25.4040605@gmail.com> <7f95d3561001220517k4fd93c6btdda02fd06596e97f@mail.gmail.com> <20100122154551.GB4020@ednor.casa.cgf.cx> <7f95d3561001220823md77as48d8128d396c8370@mail.gmail.com> <4B59D9FC.3070307@gmail.com> <7f95d3561001220923i60a15fe6u71c36b0baeda3ebe@mail.gmail.com> In-Reply-To: <7f95d3561001220923i60a15fe6u71c36b0baeda3ebe@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 1/22/2010 10:23 AM, Eric Vautier wrote: > > AndroidApp > BUILD FAILED > C:\dev\prj\app4\AndroidApp\build.xml:343: Warning: Could not find file > C:\cygdrive\c\dev\prj\app4\Common\target\Common.jar to copy. My first thought when I see things like this isn't "oh, bad idea, DOS style paths in Cygwin". I think "oh, bad idea, absolute paths hard-coded into a build system". That makes it hard to build on any other system, because it ranges from difficult to impossible to demand that everyone install outside dependencies in the same locations. There must be a tool you can use to generate the Ant files from something higher-level, which discovers the correct paths to use. That tool could also abstract away the difference in path styles. Something like Automake, Bakefile or CMake, but which knows how to create Ant files. That's where I'd put my effort, anyway. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple