aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: About the 2.1.0 binaries.  (Read 143514 times)

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
About the 2.1.0 binaries.
« on: January 02, 2006, 06:58:36 PM »
There were some "problems" on the binaries initially uploaded:

Mac:

The current aMule.zip works only with MacOS X 10.4.x a.k.a. Tiger. Another binary, this time built on panther, will be uploaded later that works on BOTH panther and tiger. However, if you use tiger, I would still recomend to use the first one.

EDIT by lionel77:
I compiled a new binary (see below) that should work fine on both Tiger and Panther. Because of Tiger specific optimizations, we however recommend, as Kry has stated above, that Tiger users stick with the original Tiger compiled binary.

New Panther & Tiger compatible version:
Direct download: http://www.amule.org/files/details.php?file=136
ED2K-Link: aMule-2.1.0-Mac.zip

Original Tiger only version:
Direct download: http://www.amule.org/files/details.php?file=140
ED2K-Link: aMule-2.1.0-Mac_Tiger.only.zip


Windows:

The remote GUI for windows fails to connect to 2.1.0 because it thinks it's CVS. My fault. The UPDATED links for the proper binary will be uploaded soon. As in, once it finishes compilation.

EDIT:

Finished. you can download it from the usual places.

ed2k link for it: Windows Remote Gui Updated
« Last Edit: January 03, 2006, 02:14:16 AM by Kry »
Logged

NiKo87

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: About the 2.1.0 binaries.
« Reply #1 on: January 04, 2006, 03:18:50 PM »
Which are these optimizations for Tiger? I have to compile aMule because I've to apply some patches to the source code for an Italian ISP but I don't want to loose these optimizations.
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: About the 2.1.0 binaries.
« Reply #2 on: January 04, 2006, 04:10:48 PM »
I think it would be interesting if you contributed those patches of your, to ckeck them and maybe include them to the official aMule release. What are those patches for?

Regards.
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: About the 2.1.0 binaries.
« Reply #3 on: January 04, 2006, 04:17:42 PM »
heh I doubt kry likes those patches  :]
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."

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: About the 2.1.0 binaries.
« Reply #4 on: January 04, 2006, 04:54:02 PM »
Kry doubts it too  :]
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: About the 2.1.0 binaries.
« Reply #5 on: January 06, 2006, 12:07:02 AM »
Quote
Originally posted by NiKo87
Which are these optimizations for Tiger? I have to compile aMule because I've to apply some patches to the source code for an Italian ISP but I don't want to loose these optimizations.

The difference isn't in any aMule code, nor is it any patch to wxMac.  It's just that when wxMac is compiled on Tiger, certain things are conditionally-compiled in which are conditionally-compiled out when built on Panther.  So, if you are compiling on Tiger, you already have these optimizations.

There are mechanisms so that the Tiger-specific stuff is always compiled in but only used at runtime if it's running on Tiger.  I'm working on integrating those mechanisms with our build system so that future aMule releases won't need two binaries for the Mac.
Logged

NiKo87

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 49
Re: About the 2.1.0 binaries.
« Reply #6 on: January 06, 2006, 01:22:04 AM »
Quote
Originally posted by ken
Quote
Originally posted by NiKo87
Which are these optimizations for Tiger? I have to compile aMule because I've to apply some patches to the source code for an Italian ISP but I don't want to loose these optimizations.

The difference isn't in any aMule code, nor is it any patch to wxMac.  It's just that when wxMac is compiled on Tiger, certain things are conditionally-compiled in which are conditionally-compiled out when built on Panther.  So, if you are compiling on Tiger, you already have these optimizations.

There are mechanisms so that the Tiger-specific stuff is always compiled in but only used at runtime if it's running on Tiger.  I'm working on integrating those mechanisms with our build system so that future aMule releases won't need two binaries for the Mac.

Thanks for the information :)

Quote
Originally posted by skolnick
I think it would be interesting if you contributed those patches of your, to ckeck them and maybe include them to the official aMule release. What are those patches for?

Regards.

I'm not the writer of the patches, Lupz made them. In Italy we have an ISP called Fastweb, which uses a private network and those patches make users of this ISP find sources faster.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: About the 2.1.0 binaries.
« Reply #7 on: January 06, 2006, 05:48:12 AM »
Blablablah. We know about that mod. We just don't support it or give support for their users. Sorry.
Logged