[Mingw-w64-public] Blog post regarding my experience using the mingw-w64 toolchain

2010-06-11 Thread Michael Adams
I heartily thank the developers for putting together this project: it allowed me to port several pieces of software to 64-bit that I regularly use. http://unquietwiki.blogspot.com/2010/06/evening-spent-cranking-out-windows-x64.html -- Michael Adams http://www.unquietwiki.com/ --

[Mingw-w64-public] FLTK 1.1.10 for w64

2010-06-11 Thread Henry N.
Hello Zhau, the FLTK 1.1.x devel library on [1] is not usable. There are missing some basic libraries (libfltk.a, libfltk_images.a). I think the build was incomplete, because the GCC stops on such errors: FL/Fl_Menu_Item.H:91: error: cast from 'void*' to 'long int' loses precision fl_open_uri.c

Re: [Mingw-w64-public] Dwarf-2 debugging support?

2010-06-11 Thread Kai Tietz
Hello Aaron, 2010/6/11 Aaron Giles : >> > Our project (MAME) recently converted a bunch of C code to C++, and >> as a result our symbol size has bloated tremendously (EXE is now >> 280MB(!) with symbols, versus 40MB without), killing our link times. >> Our cohorts on the Linux side have not notice

Re: [Mingw-w64-public] Dwarf-2 debugging support?

2010-06-11 Thread Aaron Giles
> > Our project (MAME) recently converted a bunch of C code to C++, and > as a result our symbol size has bloated tremendously (EXE is now > 280MB(!) with symbols, versus 40MB without), killing our link times. > Our cohorts on the Linux side have not noticed any significant > difference. After some

Re: [Mingw-w64-public] Dwarf-2 debugging support?

2010-06-11 Thread JonY
On 6/11/2010 23:07, Aaron Giles wrote: > Hi there, > > Our project (MAME) recently converted a bunch of C code to C++, and as a > result our symbol size has bloated tremendously (EXE is now 280MB(!) with > symbols, versus 40MB without), killing our link times. Our cohorts on the > Linux side hav

[Mingw-w64-public] Dwarf-2 debugging support?

2010-06-11 Thread Aaron Giles
Hi there, Our project (MAME) recently converted a bunch of C code to C++, and as a result our symbol size has bloated tremendously (EXE is now 280MB(!) with symbols, versus 40MB without), killing our link times. Our cohorts on the Linux side have not noticed any significant difference. After so

Re: [Mingw-w64-public] Problem with MSYS on 64-bit

2010-06-11 Thread Doug Semler
Mercurial is a revision control system (like git, svn, etc). In other words it was fixed after the release and is in their public repository. You can safely ignore that particular test's error, the bug is in the test-suite program itself. If you want to see it be clean, you could apply the patch