aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2]

Author Topic: Win32 Binaries - for those who still have to use Win$  (Read 20413 times)

iz0bbz

  • Hero Member
  • *****
  • Karma: 57
  • Offline Offline
  • Posts: 766
  • Gort! Klaatu barada nikto!
Re: Win32 Binaries - for those who still have to use Win$
« Reply #15 on: September 19, 2008, 01:35:30 PM »

I have set up a small compilation environment on Windows, following  wiki instructions.

It compiles today's SVN regularly (well, to be honest I haven't tried to compile the monolithic app - just amulegui & alcc)

Bottomline, It may be interesting to setup a mingw cross-compiler for Windows binaries on GNU/Linux. I'll give it a chance in the future.
Logged

Radek

  • Full Member
  • ***
  • Karma: 5
  • Offline Offline
  • Posts: 149
Re: Win32 Binaries - for those who still have to use Win$
« Reply #16 on: September 19, 2008, 06:26:28 PM »

No idea, why it doesn't work any longer, but after the mentioned date, I can't compile aMule-Snapshots on any of my machines!

With Debian 4 I have the same error in Scanner.l
Code: [Select]
.../Scanner.l:195: error: 'yylex_destroy' was not declared in this scope as with MingW. It occurred on August, 10th 2008 without me making any changes in the development environment (except maybe some security update or other under Debian).

Today I experimented a little with the arguments to configure but to no avail (debug on/off, optimization on/off, and so on)...
I tried with fresh directories, unpacking under Debian and under Win$, ...

I did not try the mentioned patch for Scanner.l! If such a thing is really still necessary, there is something wrong with the sources and/or the configure process!
....

Update:
For some dependencies I had to use flex 2.3.4 on Debian4. I now installed version 2.5.33 and tried compilation again: same error! I first had to delete Scanner.cpp manually to force flex to regenerate it! After that, compilation went through!

For Debian4 the problem is solved now, as it seems. But still I wonder why it occurred at all?!

Next step: another make in MingW...
I share the same source directory for Debian and Win$. Scanner.cpp was regenerated by my Debian-based compilation. And now I also can compile the Win$-binaries again!

Just amazing!

But ok, I will not think too much about it. Scanner did make trouble some time before, as I remember.

Now I have the problem, that the freshly compiled amuled won't let me connect to it with amuleweb or amulecmd. One problem solved, next problem at the door step :-)

Cheers,
Radek
Logged
There are 10 kinds of people - those who are able to understand binary numbers and those who aren't...

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3830
  • Engines screaming
Re: Win32 Binaries - for those who still have to use Win$
« Reply #17 on: September 20, 2008, 03:31:17 PM »

There is no amuled for Windows. (Yet.)
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

iz0bbz

  • Hero Member
  • *****
  • Karma: 57
  • Offline Offline
  • Posts: 766
  • Gort! Klaatu barada nikto!
Re: Win32 Binaries - for those who still have to use Win$
« Reply #18 on: September 24, 2008, 04:37:42 PM »

Now I have the problem, that the freshly compiled amuled won't let me connect to it with amuleweb or amulecmd. One problem solved, next problem at the door step :-)

There is actually a problem on the remote packages.

Testing your "aMule-Win32-SVN20080924-gui-cmdline.zip" package against amuled on Linux (SVN, same date) I can't succed in connection neither with amulecmd.exe nor amulegui.exe . Both executables hang at the beginning, when trying to connect to amuled. The amulegui.exe main window doesn't show , while the amulegui process is still alive (this is the 'usal' behaviour when amulegui cannot connect....)

As double-check I have compiled today's amulegui & amuled SVN on windows myself, and I have no problems with them.
Logged

Radek

  • Full Member
  • ***
  • Karma: 5
  • Offline Offline
  • Posts: 149
Re: Win32 Binaries - for those who still have to use Win$
« Reply #19 on: September 26, 2008, 02:32:33 PM »

Yes, I realized that, too! As a consequence I removed all the builds after 20080809 again.

But today's build (20080926) seems to be working again - I don't have the slightest idea why!  ???
As before, I didn't change anything in my environment. I just extracted the sources and started my scripts for the actual compilation.

The only thing that changes from time to time are the wxWidgets sources. I upgrade those maybe once a week. By now I'm using version 2.8.9. Maybe that has sth to do with it.

We'll see, how that develops...
Logged
There are 10 kinds of people - those who are able to understand binary numbers and those who aren't...

Nil Einne

  • Newbie
  • *
  • Karma: 1
  • Offline Offline
  • Posts: 17
Re: Win32 Binaries - for those who still have to use Win$
« Reply #20 on: May 06, 2009, 07:54:22 PM »

Are you still compiling with debug options on? I ask because I have an annoying crash when quiting which seems to mean some of the part met files are not saved ergo I keep rehashing my downloading files :-( The ordinary log file doesn't seem to show anything useful
Logged

Radek

  • Full Member
  • ***
  • Karma: 5
  • Offline Offline
  • Posts: 149
Re: Win32 Binaries - for those who still have to use Win$
« Reply #21 on: May 07, 2009, 07:12:10 PM »

No, I just forgot to change the text in the first post (but I did that now).

At the moment I compile without debug and with optimizations to keep the generated executables smaller (my upload is not the best).

But if you need a version with full debug enabled, let me know - I'll produce one out of some hat or other :)
No big problem.
Logged
There are 10 kinds of people - those who are able to understand binary numbers and those who aren't...
Pages: 1 [2]