Re: configure: Detect and use tools executable extensions for makefiles. (try2)

2009-08-28 Thread Dylan Smith
On Fri, Aug 28, 2009 at 5:57 PM, John Klehm wrote: > > On Fri, Aug 28, 2009 at 3:13 PM, Dylan Smith wrote: > > (used sed to get the EXEEXT from the wine-tools/Make.rules file) > > > > When compiling Wine on windows, the non-script tools will have an .exe > > extension, but the makefile rules assum

Re: configure: Detect and use tools executable extensions for makefiles. (try2)

2009-08-28 Thread John Klehm
On Fri, Aug 28, 2009 at 3:13 PM, Dylan Smith wrote: > (used sed to get the EXEEXT from the wine-tools/Make.rules file) > > When compiling Wine on windows, the non-script tools will have an .exe > extension, but the makefile rules assumed that the tools never have an > extention, so try to incorrect

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-27 Thread Alexandre Julliard
Dylan Smith writes: > There is no problem with running something with an exe suffix, it is > the Makefile rules that are causing the trouble. > > For instance, when building a program, this seems to be invoked: > $ gcc ../../tools/wrc/wrc.o -o ../../tools/wrc/wrc > which naturally leads to un

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-27 Thread Dylan Smith
On Thu, Aug 27, 2009 at 10:02 AM, Alexandre Julliard wrote: > Any decent shell should be able to run apps without .exe suffix on > Windows. There is no problem with running something with an exe suffix, it is the Makefile rules that are causing the trouble. For instance, when building a program,

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-27 Thread Alexandre Julliard
Steven Edwards writes: > On Thu, Aug 27, 2009 at 9:01 AM, Steven Edwards wrote: >>> I am using mingw, msysgit, msys, and some GnuWin32 packages, so it is >>> possible that it is a configuration issue.  I'll retry with only mingw >>> and msys.  I don't think they provide Flex and Bison though. >>

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-27 Thread Steven Edwards
On Thu, Aug 27, 2009 at 9:01 AM, Steven Edwards wrote: >> I am using mingw, msysgit, msys, and some GnuWin32 packages, so it is >> possible that it is a configuration issue.  I'll retry with only mingw >> and msys.  I don't think they provide Flex and Bison though. > > No they don't, I've always ha

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-27 Thread Steven Edwards
On Wed, Aug 26, 2009 at 10:52 PM, Dylan Smith wrote: > I don't know if this is new behaviour. I do remember having trouble > building on windows before, so I gave up and tried cross compiling, > which now works without errors (no -k option needed for make). > > I am using mingw, msysgit, msys, and

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-26 Thread Dylan Smith
On Wed, Aug 26, 2009 at 5:26 PM, Steven Edwards wrote: > I've never had a problem building most of Wine with cygwin or > msys+mingw before. Is this new behaviour? What do you mean by most of Wine?  I am trying to easily build all of Wine from Windows. I was able to build the whole wine tree on w

Re: configure: Detect and use tools executable extensions for makefiles.

2009-08-26 Thread Steven Edwards
On Wed, Aug 26, 2009 at 2:21 PM, Dylan Smith wrote: > When compiling Wine on windows, the non-script tools will have an .exe > extension, but the makefiles assumed that the tools never have an > extention.  Naturally this caused problems with the build, causing it to > fail on Windows. > > Please r