aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Problem compiling aMuleGui on Windows  (Read 5440 times)

Aethereal

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 35
Problem compiling aMuleGui on Windows
« on: November 14, 2005, 02:48:34 PM »

Hi all
I was able to correctly compile the windows port of aMuleGUI from 7 november, but today (14) one gives me the following error:

Code: [Select]
if g++ -DHAVE_CONFIG_H -I. -I. -I..    -I/usr/local/lib/wx/include/msw-unicode-release-static-2.6 -I/usr/local/include/wx-2.6 -D__WXMSW__ -mthreads -DNO_GCC_PRAGMA   -I./libs -DUSE_EMBEDDED_CRYPTO  -O2  -MT libmuleappcommon_a-CFile.o -MD -MP -MF ".deps/libmuleappcommon_a-CFile.Tpo" -c -o libmuleappcommon_a-CFile.o `test -f 'CFile.cpp' || echo './'`CFile.cpp; \
then mv -f ".deps/libmuleappcommon_a-CFile.Tpo" ".deps/libmuleappcommon_a-CFile.Po"; else rm -f ".deps/libmuleappcommon_a-CFile.Tpo"; exit 1; fi
In file included from ./libs/common/Format.h:29,
                 from CFile.cpp:28:
C:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/limits:290:22: macro "min" requires 2 arguments, but only 1 given
In file included from ./libs/common/Format.h:29,
                 from CFile.cpp:28:
C:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/limits:290: error: expected `;' before "throw"
C:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/limits:292: error: expected `;' before "static"
C:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../include/c++/3.4.2/limits:292:22: macro "max" requires 2 arguments, but only 1 given

I haven't changed anything since the last succesful build, and the ./config options were the same...
I was able to compile today amuled/amuleweb counterparts on Gentoo, but not the remote gui on Windows... any hint?

Thank you in advance
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: Problem compiling aMuleGui on Windows
« Reply #1 on: November 14, 2005, 03:56:12 PM »

yeah its all a little fucked up ;)

wait a couple days.... or use the one 3-4days ago that should still work
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: Problem compiling aMuleGui on Windows
« Reply #2 on: November 14, 2005, 07:46:42 PM »

It's fixed now and the fix will be in tomorrow's cvs tarball.

Anyway, if you just don't want to wait, reconfigure amule with "./configure CXXFLAGS=-DNOMINMAX", then make should do the job.
Logged
concordia cum veritate

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: Problem compiling aMuleGui on Windows
« Reply #3 on: November 15, 2005, 09:15:34 AM »

confirmed, works both here again

amule and amulegui...

but I get an assert when connecting to amule-linux fron win32 with remote-gui

aethereal can you confirum this?
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

Aethereal

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 35
Re: Problem compiling aMuleGui on Windows
« Reply #4 on: November 16, 2005, 10:59:52 AM »

Sorry for the delay...

yes, amuled compiled fine, and so did amulegui on Win with CVS-20051115, but amulegui exit on connect...

In addition, I am experiencing random problems with amuleweb on gentoo... it does not allow connections until I set --no-php -t chicane (my old settings), then it still use PHP parsing (i.e. ugly progress bars  :P ) but I suppose it is only due to the php-only migration advancing  ;)
Logged