From: Earnie B. <ea...@us...> - 2012-04-27 12:24:16
|
On Fri, Apr 27, 2012 at 3:24 AM, Jared Maddox <abs...@gm...> wrote: >> Date: Fri, 27 Apr 2012 09:11:26 +0300 >> From: Eli Zaretskii <el...@gn...> >> Subject: Re: [Mingw-users] compiler generated dependencies >> To: LM <lm...@ya...> >> Cc: min...@li... >> Message-ID: <833...@gn...> >> Content-Type: text/plain; charset=iso-8859-1 >> >>> Date: Thu, 26 Apr 2012 14:47:43 -0700 (PDT) >>> From: LM <lm...@ya...> >>> >>> Am trying to get some Open Source programs to build on Windows >>> with MinGW and msys.? A couple of them create dependency files >>> .d (using a command like gcc -M).? The output is showing up in >>> a format starting with something similar to c:\mingw\bin\../? >>> The scripts seem to want the files in a format starting with >>> something like /mingw/bin/../? Is there a setting I can adjust >>> (mount settings in /etc/fstab, environment variables, etc.) to >>> make the output more like what the script expects or do the >>> build scripts/makefiles need to be changed? >> >> What exactly do the makefiles/scripts expect that make >> c:\mingw\bin\../foo undesirable? Commands and scripts that work on >> Windows should generally grok both forward- and back-slashes alike, so >> having mixed forward- and back-slashes in a file name is quite normal. >> > > >From reading the post, it looks like the scripts expect *nix style > paths instead of Windows style paths. Is that what you meant, LM? Yes, but what scripts? In general dependency tracking happens in many projects without issue so a better understanding of what is happening needs to happen before we try to guess what is wrong. -- Earnie -- https://sites.google.com/site/earnieboyd |