Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Eight_G]

Hi all,

I'm happy for aMule 2.0.0 final releasing and I hope that this will fix a lot of problems.

Since a month ago I only compiled amuled/amuleweb without GUI (this because I dont need X-Free on my linux box).

This worked fine (although some problem due not stable version).

Going here http://www.amule.org/wiki/index.php/HowTo_Compile_aMuled

we can read:

--CUT--
2nd

Download amule-cvs from http://amule.hirnriss.net

Don't use version 2.0.0-rc8, there was a severe bug in it concerning aMuled!
Unpack it, and do as user

./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon
make
--CUT--

So until this moment I just got latest CVS snapshot and compiled it as suggested.

In changelog of aMule 2.0.0 final release I seen:

--CUT--
For users, who already got used to amulecmd's or amuleweb's command-line parameters: PLEASE READ DOCUMENTATION CAREFULLY!
--CUT--

The question is: can I use the aMule 2.0.0 final's tarball and compile it using the same options than before (./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon)?
Download latest CVS snapshot is STILL needed, can I compile amuled/amuleweb from tarball of final release?

Thanks.

Bepp0.

[stefanero]

yeah compilation is still the same....
only hte usage of the commands to start and setup amuleweb amulecmd has changed since rc8, but you have been using cvs already so you should not care much

stefanero