From: Jared M. <abs...@gm...> - 2012-04-27 07:24:30
|
> 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? |
From: LM <lm...@ya...> - 2012-04-30 23:08:48
|
Eli Zaretskii wrote: >>> 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. > Jared Maddox wrote: >From reading the post, it looks like the scripts expect *nix style >paths instead of Windows style paths. Is that what you meant, LM? Correct the scripts appear to be expecting Linux/Unix style forward slash format only. They can't handle the backslash or drive letters. So, the mixed slashes format is normal with MinGW? There's nothing wrong with this? Earnie wrote: >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. One project is a Linux program I'm trying to port, so I guess I shouldn't be surprised that it chokes on the Windows syntax. The first time I ran into this issue was with SDL 2.0 (which is a cross-platform library). It was having trouble with the OpenGL header files being in a directory under c:\mingw... I asked on the SDL mailing list and they said they were having no such trouble on their machines and that my installation of MinGW was probably broken. I'd just recently installed the latest version of MinGW when I hit the issue too and several other projects I'd built on the machine gave me no problems with compiling and linking. So, I thought that was unlikely. It did lead me to wonder whether there was something that could be set up with MinGW that could cause gcc to list dependencies using a more Linux like syntax or whether the problem was with their scripts after all. Has anyone been able to build SDL 2.0 on Windows with MinGW? I was able to get it to build if I wiped out the .d files, but otherwise it failed. Thanks. Laura http://www.distasis.com/cpp |
From: Eli Z. <el...@gn...> - 2012-05-01 02:49:23
|
> Date: Mon, 30 Apr 2012 16:08:40 -0700 (PDT) > From: LM <lm...@ya...> > > So, the mixed slashes format is normal with MinGW? There's nothing > wrong with this? Yes, this is normal. |
From: Earnie B. <ea...@us...> - 2012-05-01 12:37:20
|
On Mon, Apr 30, 2012 at 7:08 PM, LM <lm...@ya...> wrote: > Eli Zaretskii wrote: >>>> 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. >> > Jared Maddox wrote: > >From reading the post, it looks like the scripts expect *nix style >>paths instead of Windows style paths. Is that what you meant, LM? > > Correct the scripts appear to be expecting Linux/Unix style forward slash > format only. They can't handle the backslash or drive letters. So, the > mixed slashes format is normal with MinGW? There's nothing wrong with this? > While mixed slashes format is normal any POSIX shell will treat \ as an escape character where the next character following the \ may be treated specially such as \r\n would become CRLF characters. The work around for this is to apply a sed script to the generated files if the shell is going to be reading them to convert \ to /. > Earnie wrote: >>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. > > One project is a Linux program I'm trying to port, so I guess I shouldn't > be surprised that it chokes on the Windows syntax. The first time I ran > into this issue was with SDL 2.0 (which is a cross-platform library). It You'll need to determine what the shell script is doing with the dependencies. Perhaps the script could do the sed translation before reading the file. > was having trouble with the OpenGL header files being in a directory under > c:\mingw... I asked on the SDL mailing list and they said they were having > no such trouble on their machines and that my installation of MinGW was > probably broken. I'd just recently installed the latest version of MinGW > when I hit the issue too and several other projects I'd built on the machine > gave me no problems with compiling and linking. So, I thought that was > unlikely. It did lead me to wonder whether there was something > that could be set up with MinGW that could cause gcc to list dependencies > using > a more Linux like syntax or whether the problem was with their scripts after > all. Has anyone been able to build SDL 2.0 on Windows with MinGW? I was > able to get it to build if I wiped out the .d files, but otherwise it > failed. >From what I remember I just used configure, make and make install to generate a working SDL library with source downloaded from libsdl.org. I didn't have to do anything special. It has been a long while though. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Earnie B. <ea...@us...> - 2012-05-01 17:06:54
|
On Tue, May 1, 2012 at 8:37 AM, Earnie Boyd <ea...@us...> wrote: > > From what I remember I just used configure, make and make install to > generate a working SDL library with source downloaded from libsdl.org. > I didn't have to do anything special. It has been a long while > though. FWIW, I just downloaded SDL-1.2.15.tar.gz and successfully did a configure && make of the system. I put the source in one directory and did a build in another directory. -- Earnie -- https://sites.google.com/site/earnieboyd |
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 |