From: Andreas V. <li...@br...> - 2010-06-19 09:35:10
|
Am Mon, 31 May 2010 17:49:26 +0800 schrieb Mat: > Hi, Hello Mat, > My situations is , I got error "program too big to fit in memory" when > execute automake, and got hanged when execute autoconf. > ( I tested it on winxp and windows7, which memories are bigger than > 1G. ) > > The program I downloaded is from mingw site: > https://sourceforge.net/projects/mingw/files/ Last time I developed windows software It worked well with mingw if I remember correct. > version is: > automake1.11-1.11-1-mingw32-bin.tar.lzma > autoconf2.5-2.64-1-mingw32-bin.tar.lzma > > My build/test environment is setup via kde-windows' emerge > http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge > > kde-windows doesn't support autotools well currently, so I download > mingw/msys and setup manually to use it. Hm, I used a clean system with a Mingw/Msys installation without something KDE specific. Maybe mixing environments doesn't work here. > Would you like to share how your build suite is ( like urls, or > reference pages.. )? > Different build suite usually cause different result. So, it will be > great help for reduce > win32 porting via autools. As I said, I've no more win32 suite here as I don't develop open source windows software at the moment. Last time I provided a win32 binary I used a Linux cross compiler. That worked good. Is it possible for use to use a cross compiler setup? Maybe I could help you with this. > Cmake is just an working option for now, so please feel free to leave > patches of cmake aside temporarily, if it's not suitable for dbus-c++ > developing.. Let's keep trying to find out other solutions :-) I'm no big fan of providing two build systems. As long as there's no official release I would propose to not include it into the GIT repo for now. regards Andreas |